@vanilla-extract/vite-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; README style and missing keywords are normal for this ecosystem, not spam indicators. | ai | |
| dependencies | unvetted-dep:@vanilla-extract/compiler | AI (dependencies): First-party sibling package in the vanilla-extract monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@vanilla-extract/integration | AI (dependencies): First-party sibling package in the vanilla-extract monorepo; stable dependency. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 2 / 1 | |
| 5.2.1 | 2 / 1 | |
| 5.2.0 | 2 / 1 | |
| 5.1.5 | 2 / 1 | |
| 5.1.4 | 2 / 1 | |
| 5.1.3 | 2 / 1 | |
| 5.1.2 | 2 / 1 | |
| 5.1.1 | 2 / 1 | |
| 5.1.0 | 2 / 1 | |
| 5.0.7 | 2 / 1 | |
| 5.0.6 | 2 / 1 | |
| 5.0.5 | 2 / 1 | |
| 5.0.4 | 2 / 1 | |
| 5.0.3 | 2 / 1 | |
| 5.0.2 | 2 / 1 |
v5.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.