joi-multiaddr
Validate a multiaddr and common formats
joi-multiaddr@4.0.0 was published on 2019-01-04. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All joi-multiaddr versions · Permanent reference to 4.0.0
Package specifications
| Version | 4.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-01-04T17:37:26.615Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 7.88 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 11 |
| Repository stars | 1 |
| Repository forks | 1 |
Install joi-multiaddr 4.0.0
npm install joi-multiaddr@4.0.0 pnpm add joi-multiaddr@4.0.0 yarn add joi-multiaddr@4.0.0
Runtime dependencies
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.
- base-x@3.0.11 — indirect
- bs58@4.0.1 — indirect
- class-is@1.1.0 — indirect
- hi-base32@0.5.1 — indirect
- ip@1.1.9 — indirect
- ip-regex@2.1.0 — indirect
- is-ip@2.0.0 — indirect
- mafmt@6.0.10 — direct
- multiaddr@6.1.1 — direct
- safe-buffer@5.2.1 — indirect
- varint@5.0.2 — 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/14 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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/joi-multiaddr/4.0.0 — retrieved 2026-10-30T20:04:16.836Z
- https://api.deps.dev/v3/systems/npm/packages/joi-multiaddr/versions/4.0.0:dependencies — retrieved 2026-10-30T20:04:17.286Z
- https://api.deps.dev/v3/systems/npm/packages/joi-multiaddr/versions/4.0.0 — retrieved 2026-10-30T20:04:17.366Z
- https://api.deps.dev/v3/projects/github.com%2Ftableflip%2Fjoi-multiaddr — retrieved 2026-10-30T20:04:17.794Z