@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, so a manually published version cannot be tied back to a reviewed commit.
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 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.13.9 | 0 / 23 | |
| 0.13.8 | 0 / 23 | |
| 0.13.7 | 0 / 23 | |
| 0.13.6 | 0 / 23 | |
| 0.13.5 | 0 / 23 | |
| 0.13.4 | 0 / 23 | |
| 0.13.3 | 0 / 23 | |
| 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 | |
| 0.12.16 | 0 / 23 | |
| 0.12.15 | 0 / 23 | |
| 0.12.14 | 0 / 23 | |
| 0.12.13 | 0 / 23 | |
| 0.12.12 | 0 / 23 | |
| 0.12.11 | 0 / 23 | |
| 0.12.10 | 0 / 23 | |
| 0.12.9 | 0 / 23 | |
| 0.12.8 | 0 / 23 | |
| 0.12.7 | 0 / 23 | |
| 0.12.6 | 0 / 22 | |
| 0.12.5 | 0 / 22 | |
| 0.12.4 | 0 / 22 | |
| 0.12.3 | 0 / 22 | |
| 0.12.2 | 0 / 22 |
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.