rollup-plugin-svelte
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Known sveltejs maintainer handoff, stable for 860+ days, not a takeover pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate maintainer addition within sveltejs org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by stable, low-churn plugin; no malicious pattern found. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Resolves local package.json for compiler config; dual-use pattern, no hostile target. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.2.3 | 2 / 6 | |
| 7.2.2 | 2 / 7 | |
| 7.2.1 | 2 / 7 | |
| 7.2.0 | 2 / 7 | |
| 7.1.6 | 2 / 7 | |
| 7.1.5 | 2 / 6 | |
| 7.1.4 | 2 / 6 | |
| 7.1.3 | 2 / 6 | |
| 7.1.2 | 1 / 6 | |
| 7.1.0 | 2 / 6 | |
| 7.0.0 | 2 / 6 |
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
2 findingsThis version was published by a different npm account (dummdidumm) than the most recent previously approved version (conduitry) on 2024-06-05. It has since remained available on npm for 774 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findingsThis version was published by a different npm account (dummdidumm) than the most recent previously approved version (conduitry) on 2024-03-11. It has since remained available on npm for 860 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (conduitry) than the most recent previously approved version (rich_harris) on 2023-06-26, but conduitry is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.