@putout/engine-runner
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @putout/ scoped package from the same monorepo author; not a third-party supply-chain risk. | ai | |
| phantom-deps | phantom-dep:jessy | AI (phantom-deps): Config-referenced only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:nessy | AI (phantom-deps): Config-referenced only; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with long track record; no provenance is common for this ecosystem. | ai | |
| phantom-deps | phantom-dep:wraptile | AI (phantom-deps): wraptile is a declared runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 28.3.0 | 14 / 12 | |
| 28.2.2 | 14 / 13 | |
| 28.2.0 | 14 / 13 | |
| 28.0.3 | 13 / 13 | |
| 28.0.0 | 13 / 13 | |
| 27.3.1 | 13 / 13 | |
| 27.3.0 | 13 / 13 | |
| 27.1.0 | 13 / 13 | |
| 27.0.5 | 13 / 13 | |
| 27.0.0 | 15 / 13 | |
| 26.0.3 | 15 / 14 | |
| 26.0.2 | 15 / 13 | |
| 26.0.1 | 15 / 13 | |
| 26.0.0 | 15 / 13 | |
| 25.2.0 | 15 / 13 |
v28.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.