@putout/cli-process-file
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established putout monorepo publisher; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:samadhi | AI (dependencies): samadhi is a putout-ecosystem utility by the same author (coderaiser); stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@putout/eslint | AI (dependencies): @putout/eslint is an internal putout monorepo package by the same author; stable false positive. | ai | |
| phantom-deps | phantom-dep:samadhi | AI (phantom-deps): Monorepo package; samadhi referenced in config files, not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:try-catch | AI (phantom-deps): Monorepo package; try-catch referenced in config files, not a true phantom dep. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 6 / 10 | |
| 6.0.2 | 6 / 10 | |
| 6.0.1 | 6 / 10 | |
| 6.0.0 | 6 / 10 | |
| 5.1.1 | 6 / 10 | |
| 5.1.0 | 6 / 10 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.