native-dns 0.4.0
Replacement for the core DNS module, includes server implementation
native-dns@0.4.0 was published on 2013-01-10. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.5.0.
All native-dns versions · Permanent reference to 0.4.0 · Latest release
Package specifications
| Version | 0.4.0 |
|---|---|
| License declaration | Not declared |
| Published | 2013-01-10T01:16:17.334Z |
| Node.js requirement | >= 0.5.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dns.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 580 |
| Repository forks | 151 |
Install native-dns 0.4.0
npm install native-dns@0.4.0 pnpm add native-dns@0.4.0 yarn add native-dns@0.4.0
Runtime dependencies
- buffercursor >= 0.0.5
- binaryheap >= 0.0.2
- ipaddr.js >= 0.1.1
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- assert-plus@1.0.0 — indirect
- binaryheap@0.0.3 — direct
- buffercursor@0.0.12 — direct
- core-util-is@1.0.2 — indirect
- extsprintf@1.4.1 — indirect
- ipaddr.js@2.5.0 — direct
- verror@1.10.1 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — project is archived |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/native-dns/0.4.0 — retrieved 2026-10-30T19:31:11.485Z
- https://api.deps.dev/v3/systems/npm/packages/native-dns/versions/0.4.0 — retrieved 2026-10-30T19:31:11.895Z
- https://api.deps.dev/v3/systems/npm/packages/native-dns/versions/0.4.0:dependencies — retrieved 2026-10-30T19:31:11.893Z
- https://api.deps.dev/v3/projects/github.com%2Ftjfontaine%2Fnode-dns — retrieved 2026-10-30T19:31:12.565Z