← Home

caching-transform

npm Repository Homepage

Wraps a transform and provides caching

10
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

bcoecoreyfarrellnovemberbornsindresorhusvdemedes

Keywords

transformcacherequiretranspilefastspeedhash

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Documented legitimate transfer to istanbuljs org; coreyfarrell is a trusted publisher with strong track record and the repo URL confirms istanbuljs ownership. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (bcoe, coreyfarrell, novemberborn, vdemedes) are all recognized contributors in the Istanbul/nyc ecosystem — legitimate org transfer. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of jamestalmage is consistent with the documented transfer of caching-transform to the istanbuljs organization. ai
publish-pattern new-deps-added AI (publish-pattern): hasha is a well-known, trusted hashing utility replacing md5-hex — a benign dependency swap with no malicious indicators. ai

Versions (showing 10 of 10)

Version Deps Published
4.0.0 4 / 7
3.0.2 4 / 7
3.0.1 4 / 7
2.0.0 4 / 7
1.0.1 3 / 7
1.0.0 3 / 7
0.0.4 2 / 7
0.0.3 1 / 7
0.0.2 1 / 7
0.0.1 1 / 7

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

2 findings
HIGH Publisher changed: sindresorhus → coreyfarrell (on 2019-01-19) provenance

This version was published by a different npm account than previous versions on 2019-01-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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