query-registry
Query the npm registry for packuments, manifests, packages and download counts
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:zod-package-json | AI (dependencies): zod-package-json is a purpose-appropriate dependency for a package that queries and validates npm registry data; its use is expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 30 versions and consistent publisher history; lack of Sigstore provenance is common and not a security concern here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 5 / 13 | |
| 4.2.0 | 5 / 11 | |
| 4.1.0 | 6 / 11 | |
| 4.0.1 | 6 / 11 | |
| 4.0.0 | 6 / 11 | |
| 3.0.1 | 6 / 10 | |
| 3.0.0 | 6 / 10 |
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.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.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.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.