validate-npm-package-name 5.0.0
Give me a string and I'll tell you if it's a valid npm package name
validate-npm-package-name@5.0.0 was published on 2022-10-14. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^14.17.0 || ^16.13.0 || >=18.0.0.
All validate-npm-package-name versions · Permanent reference to 5.0.0 · Latest release
Package specifications
| Version | 5.0.0 |
|---|---|
| License declaration | ISC |
| Published | 2022-10-14T05:22:33.343Z |
| Node.js requirement | ^14.17.0 || ^16.13.0 || >=18.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 7.69 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/ |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 317 |
| Repository forks | 53 |
Install validate-npm-package-name 5.0.0
npm install validate-npm-package-name@5.0.0 pnpm add validate-npm-package-name@5.0.0 yarn add validate-npm-package-name@5.0.0
Runtime dependencies
- builtins ^5.0.0
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.
- builtins@5.1.0 — direct
- semver@7.8.5 — 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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Security-Policy | 10/10 — security policy file detected |
| Code-Review | 10/10 — all changesets reviewed |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 0/10 — 1 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 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/validate-npm-package-name/5.0.0 — retrieved 2026-10-29T07:30:45.435Z
- https://api.deps.dev/v3/projects/github.com%2Fnpm%2Fvalidate-npm-package-name — retrieved 2026-10-29T06:03:29.413Z
- https://api.deps.dev/v3/systems/npm/packages/validate-npm-package-name/versions/5.0.0 — retrieved 2026-10-29T07:30:45.925Z
- https://api.deps.dev/v3/systems/npm/packages/validate-npm-package-name/versions/5.0.0:dependencies — retrieved 2026-10-29T07:30:45.950Z