@vanilla-extract/rollup-plugin
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): askoufis is a known vanilla-extract contributor; addition aligns with org's CI/CD migration. | ai | |
| provenance | publisher-changed | AI (provenance): vanilla-extract-css org publishes via GitHub Actions with SLSA attestation; this is the expected CI/CD publishing pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; README and metadata patterns are typical for vanilla-extract sub-packages, not spam. | ai | |
| dependencies | unvetted-dep:@vanilla-extract/integration | AI (dependencies): Internal sibling dependency within the vanilla-extract monorepo; stable false positive for this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.5.4 | 2 / 8 | |
| 1.5.3 | 2 / 7 | |
| 1.5.2 | 2 / 7 | |
| 1.5.1 | 2 / 7 | |
| 1.5.0 | 2 / 7 | |
| 1.4.3 | 2 / 7 | |
| 1.4.2 | 2 / 7 | |
| 1.4.1 | 2 / 6 | |
| 1.4.0 | 2 / 6 | |
| 1.3.17 | 1 / 6 | |
| 1.3.16 | 1 / 6 | |
| 1.3.15 | 1 / 6 | |
| 1.3.14 | 1 / 6 | |
| 1.3.13 | 1 / 6 | |
| 1.3.12 | 1 / 6 | |
| 1.3.11 | 1 / 6 | |
| 1.3.10 | 1 / 6 | |
| 1.3.9 | 1 / 6 | |
| 1.3.8 | 1 / 6 | |
| 1.3.7 | 1 / 6 | |
| 1.3.6 | 1 / 6 | |
| 1.3.5 | 1 / 6 | |
| 1.3.4 | 1 / 6 | |
| 1.3.3 | 1 / 6 | |
| 1.3.2 | 1 / 6 | |
| 1.3.1 | 1 / 6 | |
| 1.3.0 | 1 / 6 | |
| 1.2.2 | 1 / 6 | |
| 1.2.1 | 1 / 6 | |
| 1.2.0 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.4 | 1 / 6 | |
| 1.0.3 | 1 / 6 | |
| 1.0.2 | 1 / 7 | |
| 1.0.1 | 1 / 7 | |
| 1.0.0 | 1 / 7 |
v1.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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-03-28. It has since remained available on npm for 1215 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.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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.