svelte-preprocess
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 | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance for sveltejs org package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature package under active org; dormancy reflects stability, not abandonment. | ai | |
| provenance | missing-githead | AI (provenance): Expected when switching to GitHub Actions publishing with SLSA provenance. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is a plain echo reminder; no code execution or network access. Stable pattern for this package. | ai |
v6.0.5
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.
This version was published by a different npm account than previous versions on 2026-05-25. 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.
v6.0.4
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.
This version was published by a different npm account than previous versions on 2026-05-22. 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.
v6.0.3
2 findingsScript: echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.