← Home

@vanilla-extract/compiler

npm Repository
20
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

vanilla-extract-cssmattsjonesmjt01jahredhopeaskoufis

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package publishes via GitHub Actions CI with SLSA attestation; publisher=GitHub Actions is the expected pattern for this org. ai
maintainer-change maintainer-added AI (maintainer-change): askoufis is a known vanilla-extract contributor; addition is consistent with legitimate project maintenance. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; sparse README and no keywords are expected for internal compiler packages. ai
dependencies unvetted-dep:@vanilla-extract/integration AI (dependencies): Sibling package within the same vanilla-extract-css monorepo; not an external risk. ai

Versions (showing 20 of 20)

Version Deps Published
0.7.2 4 / 0
0.7.1 4 / 0
0.7.0 4 / 0
0.6.0 4 / 0
0.5.1 4 / 0
0.5.0 4 / 0
0.4.0 4 / 0
0.3.4 4 / 0
0.3.3 4 / 0
0.3.2 4 / 0
0.3.1 4 / 0
0.3.0 4 / 0
0.2.3 4 / 0
0.2.2 4 / 0
0.2.1 4 / 0
0.2.0 4 / 0
0.1.3 4 / 0
0.1.2 4 / 0
0.1.1 4 / 0
0.1.0 4 / 0

v0.7.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.7.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.