@devvit/pushnotif
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@devvit/protos | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for internal packages. | ai | |
| phantom-deps | phantom-dep:@devvit/shared | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for internal packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK sub-package; sparse README/metadata is expected for monorepo components. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.12.24 | 3 / 6 | |
| 0.12.23 | 3 / 6 | |
| 0.12.22 | 3 / 6 | |
| 0.12.21 | 3 / 6 | |
| 0.12.20 | 3 / 6 | |
| 0.12.19 | 3 / 6 | |
| 0.12.18 | 3 / 6 | |
| 0.12.17 | 3 / 6 | |
| 0.12.16 | 3 / 6 | |
| 0.12.15 | 3 / 6 | |
| 0.12.14 | 3 / 6 | |
| 0.12.13 | 3 / 6 | |
| 0.12.12 | 3 / 6 | |
| 0.12.11 | 3 / 6 | |
| 0.12.10 | 3 / 6 | |
| 0.12.9 | 3 / 6 | |
| 0.12.8 | 3 / 6 | |
| 0.12.7 | 3 / 6 | |
| 0.12.6 | 3 / 6 | |
| 0.12.5 | 3 / 6 | |
| 0.12.4 | 3 / 6 | |
| 0.12.3 | 3 / 6 | |
| 0.12.2 | 3 / 6 | |
| 0.12.1 | 3 / 6 | |
| 0.12.0 | 3 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.