@scratch/scratch-vm
Virtual Machine 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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/node/scratch-vm.js | AI (source-diff): Webpack-minified bundle; long strings are normal CSS/JS polyfill code, not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:dist/web/scratch-vm.js | AI (source-diff): Webpack-minified bundle; long strings are normal CSS/JS polyfill code, not obfuscated payloads. | ai | |
| license | copyleft-license:AGPL-3.0-only | AI (license): Scratch VM has always been AGPL-3.0; expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:arraybuffer-loader | AI (phantom-deps): arraybuffer-loader is a webpack loader referenced in config, not directly imported in JS — stable false positive for this build-tool pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established Scratch Foundation package; lack of Sigstore provenance is common and not a disqualifier here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 13.7.3 | 21 / 30 | |
| 13.7.1 | 21 / 30 | |
| 13.7.0 | 21 / 30 | |
| 13.6.12 | 21 / 30 | |
| 13.6.11 | 21 / 30 | |
| 13.6.10 | 21 / 30 | |
| 13.6.9 | 21 / 30 | |
| 13.6.8 | 21 / 30 | |
| 13.6.7 | 21 / 30 | |
| 13.6.6 | 21 / 30 | |
| 13.6.5 | 21 / 30 | |
| 13.6.4 | 21 / 30 | |
| 13.6.3 | 21 / 30 | |
| 13.6.2 | 21 / 30 | |
| 13.6.1 | 21 / 30 | |
| 13.6.0 | 21 / 30 | |
| 13.5.0 | 21 / 30 |
v13.7.3
3 findingsModified file contains 70 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 68 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[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.7.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.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.10
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.8
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.7
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.4
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.1
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.