@chocolatey-software/build-tools
Chocolatey Software build tools.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): Build tool invoked via CLI; phantom-dep is false positive for this package type. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): Config-driven tool; phantom-dep is false positive for this package type. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): Build tool invoked via CLI; phantom-dep is false positive for this package type. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Config-driven tool; phantom-dep is false positive for this package type. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 13 / 0 | |
| 2.6.0 | 13 / 0 | |
| 2.5.0 | 13 / 0 | |
| 2.0.0 | 13 / 0 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.