read-package-json 2.0.3

The thing npm uses to read package.json files with semantics and defaults and validation

read-package-json@2.0.3 was published on 2016-01-13. Its manifest declares 4 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.

Deprecated: This package is no longer supported. Please use @npmcli/package-json instead.

All read-package-json versions · Permanent reference to 2.0.3 · Latest release

Package specifications

Version2.0.3
License declarationISC
Published2016-01-13T00:30:19.052Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count1
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 entryread-json.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies28
Repository stars224
Repository forks79

Install read-package-json 2.0.3

npm install read-package-json@2.0.3
pnpm add read-package-json@2.0.3
yarn add read-package-json@2.0.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

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.

Code-Review8/10 — Found 7/8 approved changesets -- score normalized to 8
Maintained0/10 — project is archived
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
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
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness