@chocolatey-software/blog
Chocolatey Software theme assets for use on blog.chocolatey.org.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped org package from Chocolatey Software; no plausible impersonation of 'glob'. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Asset bundle; deps referenced in build/config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:prismjs | AI (phantom-deps): Asset bundle; deps referenced in build/config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:anchor-js | AI (phantom-deps): Asset bundle; deps referenced in build/config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Asset bundle; deps referenced in build/config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-free | AI (phantom-deps): Asset bundle; deps referenced in build/config files, not direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.9.1 | 5 / 4 | |
| 2.9.0 | 5 / 4 | |
| 2.8.0 | 5 / 4 | |
| 2.7.0 | 5 / 4 | |
| 2.6.0 | 5 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.0 | 5 / 4 |
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.