validate-npm-package-name 6.0.2

Give me a string and I'll tell you if it's a valid npm package name

validate-npm-package-name@6.0.2 was published on 2025-07-21. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^18.17.0 || >=20.5.0.

All validate-npm-package-name versions · Permanent reference to 6.0.2 · Latest release

Package specifications

Version6.0.2
License declarationISC
Published2025-07-21T21:19:27.141Z
Node.js requirement^18.17.0 || >=20.5.0
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size7.71 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entrylib/
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars317
Repository forks53

Install validate-npm-package-name 6.0.2

npm install validate-npm-package-name@6.0.2
pnpm add validate-npm-package-name@6.0.2
yarn add validate-npm-package-name@6.0.2

Runtime dependencies

  • None declared

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.

    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-Artifacts10/10 — no binaries found in the repo
    Security-Policy10/10 — security policy file detected
    Code-Review10/10 — all changesets reviewed
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Maintained0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    SAST8/10 — SAST tool detected but not run on all commits

    Evidence and freshness