← Home

@vanilla-extract/rollup-plugin

npm Repository Homepage
11
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
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 11 of 11)

Version Deps Published
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

v1.5.3

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.

v1.5.2

2 findings
HIGH Publisher changed: vanilla-extract-css → GitHub Actions (on 2026-03-15) provenance

This version was published by a different npm account than previous versions on 2026-03-15. This could indicate a legitimate maintainer transition or an account compromise.

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.

v1.5.1

2 findings
HIGH Publisher changed: vanilla-extract-css → GitHub Actions (on 2025-12-16) provenance

This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.

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.

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.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.

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.17

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.

v1.3.16

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.

v1.3.15

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.