@devvit/runtime-lite
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:quickjs-emscripten-core | AI (npm-metadata): DevDependency pointing to local bundled QuickJS WASM tarballs; stable pattern for this package. | ai | |
| npm-metadata | url-dep:@jitl/quickjs-singlefile-browser-debug-sync | AI (npm-metadata): DevDependency pointing to local bundled QuickJS WASM tarballs; stable pattern for this package. | ai | |
| npm-metadata | url-dep:@jitl/quickjs-singlefile-browser-release-sync | AI (npm-metadata): DevDependency pointing to local bundled QuickJS WASM tarballs; stable pattern for this package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Intentional eval of user app bundles in Reddit's Devvit runtime; core design pattern stable across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 0 / 23 | |
| 0.13.0 | 0 / 23 | |
| 0.12.24 | 0 / 23 | |
| 0.12.23 | 0 / 23 | |
| 0.12.22 | 0 / 23 | |
| 0.12.21 | 0 / 23 | |
| 0.12.20 | 0 / 23 | |
| 0.12.19 | 0 / 23 | |
| 0.12.18 | 0 / 23 | |
| 0.12.17 | 0 / 23 |
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
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 (colacadstink) than the most recent previously approved version (devvit-cli-bot) on 2026-05-26, but colacadstink 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.
v0.12.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.