@vanilla-extract/integration
Zero-runtime Stylesheets-in-TypeScript
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): vanilla-extract-css publishes via GitHub Actions CI with SLSA attestation; publisher=GitHub Actions is expected for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package in a large monorepo; sparse README and no keywords are normal for internal integration packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.10 | 10 / 1 | |
| 8.0.9 | 10 / 1 | |
| 8.0.8 | 10 / 1 | |
| 8.0.7 | 10 / 1 | |
| 8.0.6 | 10 / 1 | |
| 8.0.5 | 10 / 1 | |
| 8.0.4 | 10 / 1 | |
| 8.0.3 | 10 / 1 | |
| 8.0.2 | 10 / 1 |
v8.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.9
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.
v8.0.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-15. 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.
v8.0.7
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v8.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.