@devvit/payments
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): SDK package in a large monorepo; sparse README/keywords is expected for internal tooling packages. | ai | |
| dependencies | unvetted-dep:@devvit/server | AI (dependencies): Sibling package in the same @devvit monorepo; unvetted status is a pipeline gap, not a risk. | ai | |
| dependencies | unvetted-dep:@devvit/public-api | AI (dependencies): Sibling package in the same @devvit monorepo; unvetted status is a pipeline gap, not a risk. | ai | |
| dependencies | unvetted-dep:@devvit/shared-types | AI (dependencies): Sibling package in the same @devvit monorepo; unvetted status is a pipeline gap, not a risk. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.13.10 | 4 / 7 | |
| 0.13.9 | 4 / 7 | |
| 0.13.8 | 4 / 7 | |
| 0.13.7 | 4 / 7 | |
| 0.13.6 | 4 / 7 | |
| 0.13.5 | 4 / 7 | |
| 0.13.4 | 4 / 7 | |
| 0.13.3 | 4 / 7 | |
| 0.13.2 | 4 / 7 | |
| 0.13.0 | 4 / 7 | |
| 0.12.24 | 4 / 7 | |
| 0.12.23 | 4 / 7 | |
| 0.12.22 | 4 / 7 | |
| 0.12.21 | 4 / 7 | |
| 0.12.20 | 4 / 7 | |
| 0.12.19 | 4 / 7 | |
| 0.12.18 | 4 / 7 | |
| 0.12.17 | 4 / 7 | |
| 0.12.16 | 4 / 7 | |
| 0.12.15 | 4 / 7 | |
| 0.12.14 | 4 / 7 | |
| 0.12.13 | 4 / 7 | |
| 0.12.12 | 4 / 7 | |
| 0.12.11 | 4 / 7 | |
| 0.12.10 | 4 / 7 | |
| 0.12.9 | 4 / 7 | |
| 0.12.8 | 4 / 7 | |
| 0.12.7 | 4 / 7 | |
| 0.12.6 | 4 / 7 | |
| 0.12.5 | 4 / 7 | |
| 0.12.4 | 4 / 7 | |
| 0.12.3 | 4 / 7 | |
| 0.12.2 | 4 / 7 | |
| 0.12.1 | 3 / 7 | |
| 0.12.0 | 3 / 7 | |
| 0.11.19 | 3 / 7 | |
| 0.11.18 | 3 / 7 | |
| 0.11.17 | 3 / 7 | |
| 0.11.16 | 3 / 7 | |
| 0.11.15 | 3 / 7 | |
| 0.11.14 | 3 / 7 | |
| 0.11.13 | 3 / 7 | |
| 0.11.12 | 3 / 7 | |
| 0.11.11 | 3 / 7 | |
| 0.11.10 | 3 / 7 | |
| 0.11.9 | 3 / 7 | |
| 0.11.8 | 3 / 7 | |
| 0.11.7 | 3 / 7 | |
| 0.11.6 | 3 / 7 | |
| 0.11.5 | 3 / 7 | |
| 0.11.4 | 3 / 7 | |
| 0.11.3 | 3 / 7 | |
| 0.11.2 | 3 / 7 | |
| 0.11.1 | 3 / 7 | |
| 0.11.0 | 3 / 7 |
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.