vite-plugin-pwa
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Result of migration to CI/CD trusted publishing with SLSA provenance; stable. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug used in config/runtime not direct import; benign for this package. | ai | |
| phantom-deps | phantom-dep:pretty-bytes | AI (phantom-deps): Referenced in build output sizing; benign. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 5 / 25 | |
| 1.2.0 | 5 / 25 | |
| 1.1.0 | 5 / 25 | |
| 1.0.3 | 5 / 25 | |
| 1.0.2 | 5 / 24 | |
| 1.0.1 | 5 / 24 | |
| 1.0.0 | 5 / 24 |
v1.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (userquin) on 2025-10-13, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.