@scratch/scratch-svg-renderer
SVG renderer for Scratch
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:base64-loader | AI (dependencies): base64-loader is a standard webpack loader used in build config; no malicious indicators for this package. | ai | |
| phantom-deps | phantom-dep:base64-loader | AI (phantom-deps): base64-loader is a webpack loader used in build config; not directly imported in source but legitimately used at build time. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 13.7.3 | 7 / 18 | |
| 13.7.2 | 7 / 18 | |
| 13.7.1 | 7 / 18 | |
| 13.6.12 | 7 / 18 | |
| 13.6.11 | 7 / 18 | |
| 13.6.10 | 7 / 18 | |
| 13.6.9 | 7 / 18 | |
| 13.6.8 | 7 / 18 | |
| 13.6.7 | 7 / 18 | |
| 13.6.6 | 7 / 18 | |
| 13.6.5 | 7 / 18 | |
| 13.6.4 | 7 / 18 | |
| 13.6.3 | 7 / 18 | |
| 13.6.2 | 7 / 19 | |
| 13.6.1 | 7 / 19 | |
| 13.6.0 | 7 / 19 | |
| 13.5.0 | 7 / 19 | |
| 13.4.0 | 7 / 19 | |
| 13.3.0 | 7 / 19 | |
| 13.2.0 | 7 / 19 | |
| 13.1.1 | 7 / 19 | |
| 13.1.0 | 7 / 19 | |
| 13.0.2 | 7 / 19 | |
| 13.0.1 | 7 / 19 | |
| 13.0.0 | 7 / 19 | |
| 12.6.4 | 7 / 19 | |
| 12.6.3 | 7 / 19 | |
| 12.6.2 | 7 / 19 | |
| 12.6.1 | 7 / 19 |
v13.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.