npm-check 0.0.3

Check for outdated, incorrect, and unused dependencies.

npm-check@0.0.3 was published on 2014-06-09. Its manifest declares 12 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.

All npm-check versions · Permanent reference to 0.0.3 · Latest release

Package specifications

Version0.0.3
License declarationMIT
Published2014-06-09T10:55:22.392Z
Node.js requirement>=0.10.0
Type declarationsNot declared
Runtime dependency count12
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/npm-check.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars6636
Repository forks231

Install npm-check 0.0.3

npm install npm-check@0.0.3
pnpm add npm-check@0.0.3
yarn add npm-check@0.0.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained10/10 — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness