@vanilla-extract/recipes
Create multi-variant styles with a type-safe runtime API, heavily inspired by https://stitches.dev
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Org transition from seek-oss-ci to vanilla-extract-css; both are official maintainers of this project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vanilla-extract-css is the canonical org account for this project. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): seek-oss-ci replaced by vanilla-extract-css; legitimate org transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org migration; stable mature package with infrequent releases. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.5.7 | 0 / 1 | |
| 0.5.6 | 0 / 1 | |
| 0.5.5 | 0 / 1 | |
| 0.5.4 | 0 / 1 | |
| 0.5.3 | 0 / 1 | |
| 0.2.5 | 0 / 1 |
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
2 findingsThis version was published by a different npm account than previous versions on 2024-08-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis version was published by a different npm account than previous versions on 2024-08-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
2 findingsThis version was published by a different npm account than previous versions on 2024-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.