npmpackage.info

Gathering detailed insights and metrics for dns-js

Other packages similar to dns-js

dns.js

1.0.1

Plain javascript DNS protocol client (minimal)

dns-suite

1.2.13

DNS implemented in Vanilla JS for Node.js and Browsers

mdns-js-packet

0.2.0

DNS Packet handling for mdns-js

@devmehq/email-validator-js

2.0.1

Advanced Email Validation with DNS MX lookup and Mailbox Verification

Gathering detailed insights and metrics for dns-js

dns-js - 0.3.1 | npmpackage.info

dns-js

DNS packet parser for node.js

0.3.1

MIT

JavaScript

6.01 kB

760,600 2.9

Installations

npm install dns-js

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

>= 14.x

Node Version

16.17.0

NPM Version

8.15.0 Score

Supply Chain

85.2

Quality

75.2

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

1

Total

12

Closed

1

Merged

10

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

mdns-js

Download Statistics

Total Downloads

760,600

Last Day

913

Last Week

7,589

Last Month

38,923

Last Year

181,165

GitHub Statistics

MIT License

17 Stars

71 Commits

17 Forks

3 Watchers

6 Branches

7 Contributors

Updated on Sep 20, 2024

Bundle Size

16.12 kB

Minified

6.01 kB

Minified + Gzipped

Bundlephobia

Maintainers

View All 7 Contributors

Package Meta Information

Latest Version

0.3.1

Package Id

dns-js@0.3.1

Unpacked Size

116.79 kB

Size

25.19 kB

File Count

103

NPM Version

8.15.0

Node Version

16.17.0

Total Downloads

Cumulative downloads

Total Downloads

760,600

Last Day

630.4%

913

Compared to previous day

Last Week

-59.6%

7,589

Compared to previous week

Last Month

49.8%

38,923

Compared to previous month

Last Year

92.3%

181,165

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

debug qap

Dev Dependencies

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

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.

1

Code-Review

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

1

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

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

2.9

/10

Last Scanned on 2025-06-23

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