@putout/compare
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:obug | AI (dependencies): obug is a putout-ecosystem utility by the same author; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:nessy | AI (dependencies): nessy is a putout-ecosystem utility by the same author; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@putout/engine-parser | AI (dependencies): Internal putout monorepo package by the same publisher; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with long track record; lack of provenance is common and not a concern here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 19.3.1 | 6 / 10 | |
| 19.1.0 | 6 / 10 | |
| 19.0.5 | 6 / 10 | |
| 19.0.2 | 6 / 10 | |
| 18.2.0 | 6 / 11 |
v19.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.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.
v19.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.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.
v18.2.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.