@checkstack/notification-pushover-backend
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish environment change is plausible for this active package family; no other corroborating risk signals. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a recognized open-source license; acceptable for this package. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): workspace:* sibling in the @checkstack monorepo; not an external dependency. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal @checkstack org package; sparse metadata is consistent across the package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the @checkstack package family; not a per-version signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package in an established @checkstack namespace; sparse metadata is typical for org-internal libs. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.1.70 | 4 / 2 | |
| 0.1.69 | 4 / 2 | |
| 0.1.68 | 4 / 2 | |
| 0.1.67 | 4 / 2 | |
| 0.1.66 | 4 / 2 | |
| 0.1.65 | 4 / 2 | |
| 0.1.64 | 4 / 2 | |
| 0.1.63 | 4 / 2 | |
| 0.1.62 | 4 / 2 | |
| 0.1.61 | 4 / 2 | |
| 0.1.60 | 4 / 2 | |
| 0.1.59 | 4 / 2 | |
| 0.1.58 | 4 / 2 | |
| 0.1.57 | 4 / 2 | |
| 0.1.56 | 4 / 2 | |
| 0.1.55 | 4 / 2 | |
| 0.1.54 | 4 / 2 | |
| 0.1.53 | 4 / 2 | |
| 0.1.52 | 4 / 2 | |
| 0.1.51 | 4 / 2 | |
| 0.1.50 | 4 / 2 | |
| 0.1.49 | 4 / 2 | |
| 0.1.48 | 4 / 2 | |
| 0.1.47 | 4 / 2 | |
| 0.1.46 | 4 / 2 | |
| 0.1.45 | 4 / 2 | |
| 0.1.44 | 4 / 2 | |
| 0.1.43 | 4 / 2 | |
| 0.1.42 | 4 / 2 | |
| 0.1.41 | 4 / 2 | |
| 0.1.40 | 4 / 2 | |
| 0.1.39 | 4 / 2 | |
| 0.1.38 | 4 / 2 | |
| 0.1.37 | 4 / 2 | |
| 0.1.36 | 4 / 2 | |
| 0.1.35 | 4 / 2 | |
| 0.1.34 | 4 / 2 | |
| 0.1.33 | 4 / 2 | |
| 0.1.32 | 4 / 2 | |
| 0.1.31 | 4 / 2 | |
| 0.1.30 | 4 / 2 | |
| 0.1.29 | 4 / 2 | |
| 0.1.28 | 4 / 2 | |
| 0.1.27 | 4 / 2 | |
| 0.1.26 | 4 / 2 | |
| 0.1.25 | 4 / 2 | |
| 0.1.24 | 4 / 2 | |
| 0.1.23 | 4 / 2 | |
| 0.1.22 | 4 / 2 | |
| 0.1.21 | 4 / 2 | |
| 0.1.20 | 4 / 2 |
v0.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.