unplugin-swc
10
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
egoisthannoeru
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 10 of 10)
| 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 | |
| 1.5.2 | 3 / 13 | |
| 1.5.1 | 3 / 13 | |
| 1.5.0 | 3 / 13 |
v1.5.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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.