@astrojs/check
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): withastro/astro monorepo transitioned to GitHub Actions publishing with SLSA provenance attestation; publisher change reflects CI/CD modernization, not a compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of the official withastro org's workflow transition; maintainer roster changes are consistent with org-level CI/CD publishing adoption. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Sub-package of the withastro/astro monorepo; dormancy reflects no need for releases in that period, not abandonment. SLSA provenance confirms legitimate publish. | ai | |
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): @astrojs/check is the official Astro type-checking tool under the withastro org; the levenshtein match to 'chalk' is purely coincidental and not a typosquat. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.9.9 | 4 / 5 | |
| 0.9.8 | 4 / 5 | |
| 0.9.7 | 4 / 5 | |
| 0.9.6 | 4 / 5 | |
| 0.9.5 | 4 / 7 | |
| 0.9.4 | 4 / 7 |
v0.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.6
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.