engine-cache
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mixin-deep | AI (phantom-deps): Lazy-cache pattern used throughout this ecosystem; deps declared in package.json are loaded lazily via utils.js, not directly imported in index.js. | ai | |
| phantom-deps | phantom-dep:helper-cache | AI (phantom-deps): Lazy-cache pattern; dependency is loaded lazily via utils.js in this ecosystem. | ai | |
| phantom-deps | phantom-dep:async-helpers | AI (phantom-deps): Lazy-cache pattern; dependency is loaded lazily via utils.js in this ecosystem. | ai | |
| phantom-deps | phantom-dep:extend-shallow | AI (phantom-deps): Lazy-cache pattern; dependency is loaded lazily via utils.js in this ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): doowb (Brian Woodward) is an explicitly listed contributor and maintainer in package.json; this is a documented legitimate transition, not a suspicious takeover. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4275 days old, predating Sigstore provenance on npm. Absence is expected and not a risk signal for this well-established package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 5 / 15 | |
| 1.0.0 | 5 / 15 | |
| 0.19.4 | 6 / 15 | |
| 0.19.3 | 6 / 15 | |
| 0.19.2 | 6 / 15 | |
| 0.19.1 | 6 / 15 | |
| 0.19.0 | 6 / 15 | |
| 0.18.1 | 6 / 15 | |
| 0.18.0 | 6 / 15 | |
| 0.17.0 | 5 / 15 | |
| 0.16.2 | 5 / 15 | |
| 0.16.1 | 5 / 15 | |
| 0.16.0 | 4 / 15 | |
| 0.15.0 | 4 / 11 | |
| 0.14.1 | 4 / 9 | |
| 0.14.0 | 3 / 9 | |
| 0.13.0 | 3 / 8 | |
| 0.12.2 | 4 / 8 | |
| 0.12.1 | 4 / 8 | |
| 0.11.0 | 3 / 9 | |
| 0.10.6 | 6 / 9 | |
| 0.10.5 | 6 / 9 | |
| 0.10.4 | 6 / 9 | |
| 0.10.3 | 6 / 9 | |
| 0.10.2 | 7 / 9 | |
| 0.10.1 | 7 / 9 | |
| 0.10.0 | 7 / 8 | |
| 0.9.0 | 5 / 8 | |
| 0.8.0 | 5 / 5 | |
| 0.7.0 | 5 / 9 | |
| 0.6.2 | 5 / 7 | |
| 0.6.0 | 5 / 10 | |
| 0.5.1 | 5 / 9 | |
| 0.5.0 | 5 / 9 | |
| 0.4.0 | 8 / 9 | |
| 0.3.4 | 5 / 9 | |
| 0.3.3 | 5 / 9 | |
| 0.3.0 | 4 / 9 | |
| 0.2.6 | 4 / 9 | |
| 0.2.5 | 4 / 9 | |
| 0.2.3 | 4 / 9 | |
| 0.2.2 | 4 / 9 | |
| 0.2.1 | 3 / 9 | |
| 0.2.0 | 3 / 8 | |
| 0.1.3 | 2 / 8 | |
| 0.1.2 | 2 / 8 | |
| 0.1.1 | 2 / 8 | |
| 0.1.0 | 2 / 8 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
2 findingsThis version was published by a different npm account than previous versions on 2017-02-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
2 findingsThis version was published by a different npm account than previous versions on 2017-02-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
2 findingsThis version was published by a different npm account than previous versions on 2016-06-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
2 findingsThis version was published by a different npm account than previous versions on 2016-05-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
2 findingsThis version was published by a different npm account than previous versions on 2015-07-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-03-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-15. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jonschlinkert.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-11-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-11-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2014-08-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
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.