read-package-json
The thing npm uses to read package.json files with semantics and defaults and validation
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): npm CLI team packages frequently change publish environments; gitHead absence is expected for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-cli-ops and saquibkhan are known npm CLI team accounts; routine team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): darcyclarke left the npm CLI team; removal is expected. | ai | |
| provenance | no-provenance | AI (provenance): Official npm CLI package; provenance not yet adopted at time of publish. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from gar to npm-cli-ops is a known npm CLI team transition; npm-cli-ops is the shared ops account for the npm org. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 4 / 3 | |
| 7.0.0 | 4 / 3 | |
| 6.0.4 | 4 / 3 | |
| 6.0.3 | 4 / 3 | |
| 6.0.2 | 4 / 3 | |
| 6.0.1 | 4 / 3 | |
| 6.0.0 | 4 / 3 | |
| 5.0.2 | 4 / 3 | |
| 5.0.1 | 4 / 3 | |
| 5.0.0 | 4 / 2 | |
| 4.1.2 | 4 / 3 | |
| 4.1.1 | 4 / 3 | |
| 4.1.0 | 4 / 3 | |
| 4.0.1 | 4 / 3 | |
| 4.0.0 | 4 / 3 | |
| 3.0.1 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.1.2 | 4 / 3 | |
| 2.1.1 | 5 / 3 | |
| 2.1.0 | 5 / 3 | |
| 2.0.13 | 5 / 3 | |
| 2.0.12 | 5 / 2 | |
| 2.0.11 | 4 / 2 | |
| 2.0.10 | 4 / 2 | |
| 2.0.9 | 4 / 2 | |
| 2.0.8 | 4 / 2 | |
| 2.0.7 | 4 / 2 | |
| 2.0.6 | 4 / 2 | |
| 2.0.5 | 4 / 2 | |
| 2.0.4 | 4 / 2 | |
| 2.0.3 | 4 / 2 | |
| 2.0.2 | 4 / 2 | |
| 2.0.1 | 4 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.3.3 | 4 / 2 | |
| 1.3.2 | 7 / 1 | |
| 1.3.1 | 6 / 1 | |
| 1.3.0 | 6 / 1 | |
| 1.2.7 | 6 / 1 | |
| 1.2.6 | 5 / 1 | |
| 1.2.5 | 5 / 1 | |
| 1.2.4 | 4 / 1 | |
| 1.2.3 | 4 / 1 | |
| 1.2.2 | 4 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.9 | 4 / 1 | |
| 1.1.8 | 4 / 1 | |
| 1.1.7 | 4 / 1 | |
| 1.1.6 | 4 / 1 | |
| 1.1.5 | 4 / 1 |
v7.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2023-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v6.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-21. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.