@vanilla-extract/dynamic
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Long-stable org migration from seek-oss-ci to vanilla-extract-css, not recent. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org migration, stable for 1342 days. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale publisher change, inconsistent with takeover per analyzer's own note. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.5 | 1 / 1 | |
| 2.1.4 | 1 / 1 | |
| 2.1.3 | 1 / 1 | |
| 2.1.2 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.3 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
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-11-10. It has since remained available on npm for 984 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.
v2.0.3
2 findingsThis version was published by a different npm account (vanilla-extract-css) than the most recent previously approved version (seek-oss-ci) on 2022-11-16. It has since remained available on npm for 1342 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.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.