@npmcli/package-json
Programmatic API to update package.json
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from ruyadorno to gar reflects normal npm org team rotation; both are known GitHub/npm employees with strong track records. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of gimli01 and isaacs reflects normal npm org team rotation, not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fritzy is a known npm/GitHub contributor; addition is consistent with normal npm org team management. | ai | |
| dependencies | unvetted-dep:validate-npm-package-license | AI (dependencies): validate-npm-package-license is a well-known npm ecosystem utility for SPDX license validation; its use in a package.json management library is entirely appropriate and expected. | ai | |
| dependencies | unvetted-dep:@npmcli/git | AI (dependencies): @npmcli/git is an official npm org package; a stable, legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:json-parse-even-better-errors | AI (dependencies): json-parse-even-better-errors is a standard npm ecosystem utility; legitimate and expected dependency here. | ai | |
| dependencies | unvetted-dep:spdx-expression-parse | AI (dependencies): spdx-expression-parse is a well-known, widely-used SPDX license parsing library; no risk in this context. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 7 / 3 | |
| 7.0.5 | 7 / 3 | |
| 7.0.4 | 7 / 3 | |
| 7.0.3 | 7 / 3 | |
| 7.0.2 | 7 / 3 | |
| 7.0.1 | 7 / 3 | |
| 7.0.0 | 7 / 3 | |
| 6.2.0 | 7 / 5 | |
| 6.1.1 | 7 / 5 | |
| 6.1.0 | 7 / 5 | |
| 6.0.1 | 7 / 5 | |
| 6.0.0 | 7 / 5 | |
| 5.2.1 | 7 / 5 | |
| 5.2.0 | 7 / 5 | |
| 5.1.1 | 7 / 5 | |
| 5.1.0 | 7 / 5 | |
| 5.0.3 | 7 / 5 | |
| 5.0.2 | 7 / 5 | |
| 5.0.1 | 7 / 5 | |
| 5.0.0 | 7 / 5 | |
| 4.0.1 | 7 / 5 | |
| 4.0.0 | 6 / 5 | |
| 3.1.1 | 6 / 5 | |
| 3.1.0 | 4 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-17. This could indicate a legitimate maintainer transition or an account compromise.
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.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.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.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
2 findingsThis version was published by a different npm account than previous versions on 2024-04-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2024-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2024-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-08-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
2 findingsThis version was published by a different npm account than previous versions on 2023-07-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-07-05. 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.
v3.1.1
2 findingsThis version was published by a different npm account than previous versions on 2023-06-06. 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.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-05-16. 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.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.