Installations

npm install dns-js

Pull Requests

Open

1

Total

12

Closed

1

Merged

10

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Developer

mdns-js

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>= 14.x

Typescript Support

No

Node Version

16.17.0

NPM Version

8.15.0 Statistics

17 Stars

71 Commits

18 Forks

4 Watching

6 Branches

7 Contributors

Updated on 20 Sept 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

649,562

Last day

-62.4%

260

Compared to previous day

Last week

-29.2%

3,356

Compared to previous week

Last month

33%

17,052

Compared to previous month

Last year

39.3%

119,826

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

2

debug qap

Dev Dependencies

4

@hapi/code eslint @hapi/lab native-dns-packet

Versions

dns-js

DNS packet parser specifically built for mdns-js but it should be generic enough to do general dns stuff.

NEW LOCATION

This project was moved into it's own organisation and changed name from node-mdns-js-packet to node-dns-js. Please update any git remotes you might have pointing here.

git remote set-url origin https://github.com/mdns-js/node-dns-js.git

You probably want to have a look at native-dns-packet first and if that does do what you need, you might start looking at this.

dns-js should produce the same output as native-dns-packet, it even uses it's test fixtures and borrows some parts of it.

This was made before i knew about native-dns-packet but since that still has some bugs in handling some mDNS packets I cant use it.

example

1var dns = require('dns-js');
2
3/*some code that will get you a dns message buffer*/
4
5var result = dns.DNSPacket.parse(message);
6
7console.log(result);

Look at examples/dnsresolver.js for a more detailed example.

Contribute

I will gladly accept any contributions as pull requests. Just run npm run lint on the code first so that the coding style is kept somewhat consistent. I miss doing this myself from time to time and I won't go ballistic if anyone else forget but I would really appreciate it.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.1

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More