prettier-plugin-svelte
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): Transition from individual maintainer to GitHub Actions CI/CD; SLSA attestation confirms legitimate publish. | ai | |
| provenance | missing-githead | AI (provenance): Expected when switching to GitHub Actions publish workflow. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer list cleanup during CI/CD migration for official sveltejs org package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used for source map decoding in browser bundle; not a malicious payload pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified svelte5CompilerPath option; documented plugin behavior, not arbitrary code loading. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 0 / 14 | |
| 4.0.0 | 0 / 14 | |
| 3.5.2 | 0 / 12 | |
| 3.5.1 | 0 / 12 | |
| 3.5.0 | 0 / 12 | |
| 3.4.1 | 0 / 12 | |
| 3.4.0 | 0 / 12 |
v4.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v4.0.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.
This version was published by a different npm account than previous versions on 2026-05-20. 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.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.