@devvit/web-view-scripts
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo package published via publishConfig.directory=dist; empty index.js and sparse metadata are structural, not malicious. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @devvit/* packages; not a spam indicator for this publisher. | ai | |
| phantom-deps | phantom-dep:@devvit/shared | AI (phantom-deps): Same-org sibling dep; phantom-dep false positive common in monorepo packages. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.13.10 | 5 / 10 | |
| 0.13.9 | 5 / 10 | |
| 0.13.8 | 5 / 10 | |
| 0.13.7 | 5 / 10 | |
| 0.13.6 | 5 / 10 | |
| 0.13.5 | 5 / 10 | |
| 0.13.4 | 5 / 10 | |
| 0.13.3 | 5 / 10 | |
| 0.13.2 | 5 / 10 | |
| 0.13.0 | 5 / 10 | |
| 0.12.24 | 5 / 10 | |
| 0.12.23 | 5 / 10 | |
| 0.12.22 | 5 / 10 | |
| 0.12.21 | 5 / 10 | |
| 0.12.20 | 5 / 10 | |
| 0.12.19 | 5 / 10 | |
| 0.12.18 | 5 / 10 | |
| 0.12.17 | 5 / 10 | |
| 0.12.16 | 5 / 10 | |
| 0.12.15 | 5 / 10 | |
| 0.12.14 | 4 / 10 | |
| 0.12.13 | 4 / 10 | |
| 0.12.12 | 4 / 10 | |
| 0.12.11 | 4 / 10 | |
| 0.12.10 | 4 / 10 | |
| 0.12.9 | 4 / 10 | |
| 0.12.8 | 4 / 10 | |
| 0.12.7 | 4 / 10 | |
| 0.12.6 | 4 / 9 | |
| 0.12.5 | 4 / 9 | |
| 0.12.4 | 4 / 9 | |
| 0.12.3 | 4 / 7 | |
| 0.12.2 | 4 / 7 | |
| 0.12.1 | 4 / 7 | |
| 0.12.0 | 4 / 7 | |
| 0.11.19 | 2 / 7 | |
| 0.11.18 | 2 / 7 | |
| 0.11.17 | 2 / 7 | |
| 0.11.16 | 0 / 9 | |
| 0.11.15 | 0 / 6 | |
| 0.11.14 | 0 / 6 | |
| 0.11.13 | 0 / 6 | |
| 0.11.12 | 0 / 6 |
v0.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.