package-json
Get metadata of a package from the npm registry
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rc | AI (dependencies): rc is a well-known npm config library; its use in package-json for reading npm registry config is legitimate and expected. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): The added rc dependency is a well-established library with clear legitimate purpose for this package's npm registry interaction use case. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4329 days old, predates Sigstore provenance; published by highly trusted sindresorhus. Absence of provenance is expected and not a risk signal here. | ai | |
| dependencies | unvetted-dep:ky | AI (dependencies): ky is a well-known sindresorhus HTTP client library; entirely appropriate dependency for an npm registry metadata fetcher. | ai | |
| dependencies | unvetted-dep:registry-url | AI (dependencies): registry-url is a standard npm registry utility; expected dependency for this package's purpose. | ai | |
| dependencies | unvetted-dep:registry-auth-token | AI (dependencies): registry-auth-token is a standard npm registry auth utility; expected dependency for this package's purpose. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 4 / 5 | |
| 10.0.0 | 4 / 5 | |
| 9.0.0 | 4 / 5 | |
| 8.1.1 | 4 / 5 | |
| 8.1.0 | 4 / 5 | |
| 8.0.0 | 4 / 5 | |
| 7.0.0 | 4 / 5 | |
| 6.5.0 | 4 / 5 | |
| 6.4.0 | 4 / 5 | |
| 6.3.0 | 4 / 5 | |
| 6.2.0 | 4 / 4 | |
| 6.1.0 | 4 / 4 | |
| 6.0.0 | 4 / 3 | |
| 5.0.0 | 4 / 3 | |
| 4.0.1 | 4 / 3 | |
| 4.0.0 | 4 / 3 | |
| 3.1.0 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.4.0 | 4 / 3 | |
| 2.3.3 | 4 / 2 | |
| 2.3.2 | 4 / 2 | |
| 2.3.1 | 4 / 2 | |
| 2.3.0 | 4 / 2 | |
| 2.2.1 | 3 / 2 | |
| 2.2.0 | 3 / 2 | |
| 2.1.0 | 3 / 2 | |
| 2.0.1 | 3 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.2.0 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.2 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 1 / 1 |
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.