@checkstack/notification-backstage-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): Isolated publish-environment change; no other malicious signals present across 30 versions of this package. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a legitimate open-source license; stable for this package. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Internal monorepo workspace dependency; not a third-party unvetted package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack/* packages; no CI provenance setup in this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent across @checkstack scope. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 4 / 2 | |
| 0.2.5 | 4 / 2 | |
| 0.2.4 | 4 / 2 | |
| 0.2.3 | 4 / 2 | |
| 0.2.2 | 4 / 2 | |
| 0.2.1 | 4 / 2 | |
| 0.2.0 | 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 |
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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.