@scratch/scratch-render
WebGL Renderer for Scratch 3.0
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:hull.js | AI (dependencies): hull.js is a known convex-hull geometry library; stable use in a WebGL renderer. | ai | |
| dependencies | unvetted-dep:ify-loader | AI (dependencies): ify-loader is a webpack loader for browserify transforms; build-time only, no runtime risk. | ai | |
| phantom-deps | phantom-dep:linebreak | AI (phantom-deps): Referenced in config/build context, not a missing runtime dep. | ai | |
| provenance | no-provenance | AI (provenance): Established Scratch Foundation package; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:grapheme-breaker | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:raw-loader | AI (phantom-deps): Webpack loader referenced in config only. | ai | |
| phantom-deps | phantom-dep:ify-loader | AI (phantom-deps): Build-tool loader referenced in webpack config, not a runtime import. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 13.7.2 | 8 / 23 | |
| 13.7.1 | 8 / 23 | |
| 13.6.12 | 8 / 23 | |
| 13.6.11 | 8 / 23 | |
| 13.6.9 | 8 / 23 | |
| 13.6.6 | 8 / 23 | |
| 13.6.5 | 8 / 23 | |
| 13.6.3 | 8 / 23 | |
| 13.6.2 | 8 / 24 | |
| 13.6.0 | 8 / 24 | |
| 13.5.0 | 8 / 24 |
v13.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.