unplugin-swc
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publishing is backed by SLSA provenance attestation; consistent with org-level CI/CD adoption. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish with no code changes; low risk of takeover given SLSA provenance. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.5.9 | 3 / 13 | |
| 1.5.8 | 3 / 13 | |
| 1.5.7 | 3 / 13 | |
| 1.5.6 | 3 / 13 | |
| 1.5.5 | 3 / 13 | |
| 1.5.4 | 3 / 13 | |
| 1.5.3 | 3 / 13 |
v1.5.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.8
2 findingsThis version was published by a different npm account than previous versions on 2025-10-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.