← Home

pkg-cache

Gets the package.json for one or more names from the npm registry and caches the results for a specified period of time. Default cache period is one week.

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jonschlinkert

Keywords

cachedatadategetjsonpackagepackage-jsonpackagespkgsetsincestoretimetimespan

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:get-pkgs AI (phantom-deps): Dependency is explicitly declared and used; referenced in verb config as related package documentation. ai
phantom-deps phantom-dep:data-store AI (phantom-deps): Dependency is explicitly declared and used; referenced in verb config as related package documentation. ai
phantom-deps phantom-dep:date-store AI (phantom-deps): Dependency is explicitly declared and used; referenced in verb config as related package documentation. ai
phantom-deps phantom-dep:lazy-cache AI (phantom-deps): Dependency is explicitly declared and used; referenced in verb config as related package documentation. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.4 5 / 7
0.1.3 5 / 7
0.1.2 5 / 7
0.1.1 5 / 7
0.1.0 5 / 7

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.