@chocolatey-software/astro
Chocolatey Software theme assets for Astro.
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:@astrojs/check | AI (phantom-deps): Same pattern — Astro plugin declared for consumer use, not directly imported. | ai | |
| phantom-deps | phantom-dep:@astrojs/mdx | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai | |
| phantom-deps | phantom-dep:@astrojs/rss | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai | |
| phantom-deps | phantom-dep:@astrojs/node | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai | |
| phantom-deps | phantom-dep:astro | AI (phantom-deps): Astro and its integrations are referenced in config files, not JS imports — standard pattern for Astro theme packages. | ai | |
| phantom-deps | phantom-dep:@astrojs/sitemap | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai | |
| phantom-deps | phantom-dep:remark-custom-header-id | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai | |
| phantom-deps | phantom-dep:rehype-mermaid | AI (phantom-deps): Config-file-only reference; normal for Astro theme/integration packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 7 / 0 | |
| 2.7.0 | 7 / 0 | |
| 2.6.0 | 7 / 0 | |
| 2.5.0 | 7 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.0 | 8 / 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.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. Consider requesting the maintainer enable provenance via CI/CD.
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.1.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.