@devvit/builders
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@devvit/build-pack | AI (dependencies): Same @devvit org scope, pinned to matching version; sibling dep in a monorepo pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Reddit/Devvit monorepo package; sparse README and no keywords are expected for internal tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @devvit/* monorepo packages; not a malware indicator. | ai | |
| phantom-deps | phantom-dep:@devvit/shared-types | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is unreliable for monorepo transitive usage. | ai |
Versions (showing 100 of 101)
| Version | Deps | Published |
|---|---|---|
| 0.13.10 | 4 / 5 | |
| 0.13.9 | 4 / 5 | |
| 0.13.8 | 4 / 5 | |
| 0.13.7 | 4 / 5 | |
| 0.13.6 | 4 / 5 | |
| 0.13.5 | 4 / 5 | |
| 0.13.4 | 4 / 5 | |
| 0.13.3 | 4 / 5 | |
| 0.13.2 | 4 / 5 | |
| 0.13.0 | 4 / 5 | |
| 0.12.24 | 4 / 5 | |
| 0.12.23 | 4 / 5 | |
| 0.12.22 | 4 / 5 | |
| 0.12.21 | 4 / 5 | |
| 0.12.20 | 4 / 5 | |
| 0.12.19 | 4 / 5 | |
| 0.12.18 | 4 / 5 | |
| 0.12.17 | 4 / 5 | |
| 0.12.16 | 4 / 5 | |
| 0.12.15 | 4 / 5 | |
| 0.12.14 | 4 / 5 | |
| 0.12.13 | 4 / 5 | |
| 0.12.12 | 4 / 5 | |
| 0.12.11 | 4 / 5 | |
| 0.12.10 | 4 / 5 | |
| 0.12.9 | 4 / 5 | |
| 0.12.8 | 4 / 5 | |
| 0.12.7 | 4 / 5 | |
| 0.12.6 | 4 / 5 | |
| 0.12.5 | 4 / 5 | |
| 0.12.4 | 4 / 5 | |
| 0.12.3 | 4 / 5 | |
| 0.12.2 | 4 / 5 | |
| 0.12.1 | 4 / 5 | |
| 0.12.0 | 4 / 5 | |
| 0.11.19 | 4 / 5 | |
| 0.11.18 | 5 / 5 | |
| 0.11.17 | 5 / 5 | |
| 0.11.16 | 5 / 5 | |
| 0.11.15 | 5 / 5 | |
| 0.11.14 | 5 / 5 | |
| 0.11.13 | 5 / 5 | |
| 0.11.12 | 5 / 5 | |
| 0.11.11 | 5 / 5 | |
| 0.11.10 | 5 / 5 | |
| 0.11.9 | 5 / 5 | |
| 0.11.8 | 5 / 5 | |
| 0.11.7 | 5 / 5 | |
| 0.11.6 | 5 / 5 | |
| 0.11.5 | 5 / 5 | |
| 0.11.4 | 5 / 5 | |
| 0.11.3 | 5 / 5 | |
| 0.11.2 | 5 / 5 | |
| 0.11.1 | 5 / 5 | |
| 0.11.0 | 5 / 5 | |
| 0.10.25 | 6 / 6 | |
| 0.10.24 | 6 / 6 | |
| 0.10.23 | 6 / 6 | |
| 0.10.22 | 6 / 6 | |
| 0.10.21 | 6 / 6 | |
| 0.10.20 | 6 / 6 | |
| 0.10.19 | 6 / 6 | |
| 0.10.18 | 6 / 6 | |
| 0.10.17 | 6 / 6 | |
| 0.10.16 | 6 / 6 | |
| 0.10.15 | 6 / 6 | |
| 0.10.14 | 6 / 6 | |
| 0.10.13 | 6 / 6 | |
| 0.10.12 | 6 / 6 | |
| 0.10.11 | 6 / 6 | |
| 0.10.10 | 6 / 6 | |
| 0.10.9 | 6 / 6 | |
| 0.10.8 | 6 / 6 | |
| 0.10.7 | 6 / 6 | |
| 0.10.6 | 6 / 6 | |
| 0.10.5 | 6 / 6 | |
| 0.10.4 | 6 / 6 | |
| 0.10.3 | 6 / 6 | |
| 0.10.2 | 6 / 6 | |
| 0.10.1 | 6 / 6 | |
| 0.10.0 | 6 / 6 | |
| 0.9.9 | 6 / 6 | |
| 0.9.8 | 6 / 6 | |
| 0.9.7 | 6 / 6 | |
| 0.9.6 | 6 / 6 | |
| 0.9.5 | 6 / 6 | |
| 0.9.4 | 6 / 6 | |
| 0.9.3 | 6 / 6 | |
| 0.9.2 | 6 / 6 | |
| 0.9.1 | 6 / 6 | |
| 0.9.0 | 6 / 6 | |
| 0.8.11 | 6 / 6 | |
| 0.8.10 | 6 / 6 | |
| 0.8.9 | 6 / 6 | |
| 0.8.8 | 6 / 6 | |
| 0.8.7 | 6 / 6 | |
| 0.8.6 | 6 / 6 | |
| 0.8.5 | 6 / 6 | |
| 0.8.4 | 6 / 5 | |
| 0.8.3 | 6 / 5 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.