@vanilla-extract/css
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-stale | AI (provenance): Long-stale account change with clean publisher history; not a takeover pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Historical org handoff, consistent across many prior approved versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): askoufis is a known vanilla-extract contributor; addition is consistent with legitimate project governance. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — this is a CI/CD migration to a more secure publish flow, not a compromise indicator. Stable for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package has verified SLSA provenance via Sigstore; strongest supply chain integrity signal available. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @vanilla-extract/css is a well-known scoped CSS-in-TS library; levenshtein match against 'cors' is a false positive driven by the scoped package name format. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @vanilla-extract/css is a well-known scoped CSS-in-TS library; levenshtein match against 'qs' is a false positive driven by the scoped package name format. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 1.21.2 | 11 / 0 | |
| 1.21.1 | 11 / 0 | |
| 1.21.0 | 11 / 0 | |
| 1.20.1 | 11 / 0 | |
| 1.20.0 | 12 / 1 | |
| 1.19.1 | 12 / 1 | |
| 1.19.0 | 12 / 1 | |
| 1.18.0 | 12 / 1 | |
| 1.17.5 | 12 / 1 | |
| 1.17.4 | 12 / 1 | |
| 1.17.3 | 12 / 1 | |
| 1.17.2 | 12 / 1 | |
| 1.17.1 | 12 / 1 | |
| 1.17.0 | 12 / 1 | |
| 1.16.1 | 12 / 1 | |
| 1.16.0 | 12 / 1 | |
| 1.15.5 | 12 / 1 | |
| 1.15.4 | 11 / 1 | |
| 1.15.3 | 11 / 1 | |
| 1.15.2 | 11 / 1 | |
| 1.15.1 | 11 / 1 | |
| 1.15.0 | 11 / 1 | |
| 1.14.2 | 11 / 1 | |
| 1.14.1 | 11 / 1 | |
| 1.14.0 | 11 / 1 | |
| 1.13.0 | 11 / 1 | |
| 1.12.0 | 11 / 1 | |
| 1.11.1 | 11 / 1 | |
| 1.11.0 | 11 / 1 | |
| 1.10.0 | 11 / 1 | |
| 1.9.5 | 11 / 1 | |
| 1.9.4 | 11 / 1 | |
| 1.9.3 | 11 / 1 | |
| 1.9.2 | 11 / 1 | |
| 1.9.1 | 11 / 1 | |
| 1.9.0 | 11 / 1 | |
| 1.8.0 | 11 / 1 | |
| 1.7.4 | 11 / 1 | |
| 1.7.3 | 11 / 1 | |
| 1.7.2 | 11 / 1 | |
| 1.7.1 | 11 / 1 | |
| 1.7.0 | 11 / 2 | |
| 1.6.8 | 10 / 1 | |
| 1.6.7 | 10 / 1 | |
| 1.6.6 | 10 / 1 | |
| 1.6.5 | 10 / 1 | |
| 1.6.4 | 9 / 1 | |
| 1.6.3 | 9 / 1 | |
| 1.6.2 | 9 / 1 | |
| 1.6.1 | 9 / 2 | |
| 1.6.0 | 9 / 2 | |
| 1.5.1 | 9 / 2 | |
| 1.5.0 | 9 / 2 | |
| 1.4.1 | 9 / 2 | |
| 1.4.0 | 9 / 2 | |
| 1.3.0 | 8 / 2 | |
| 1.2.3 | 8 / 2 | |
| 1.2.2 | 8 / 2 | |
| 1.2.1 | 8 / 2 | |
| 1.2.0 | 8 / 2 | |
| 1.1.2 | 8 / 2 | |
| 1.1.1 | 8 / 2 | |
| 1.1.0 | 8 / 2 | |
| 1.0.1 | 8 / 2 | |
| 1.0.0 | 8 / 2 |
v1.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
2 findingsThis version was published by a different npm account (vanilla-extract-css) than the most recent previously approved version (seek-oss-ci) on 2023-01-23. It has since remained available on npm for 1275 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
2 findingsThis version was published by a different npm account (vanilla-extract-css) than the most recent previously approved version (seek-oss-ci) on 2022-11-16. It has since remained available on npm for 1342 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.