@checkstack/notification-smtp-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Same-org @checkstack scoped package; stable internal dependency pattern across versions. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a known, intentional license choice for this @checkstack org package; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Internal monorepo package; provenance absence is consistent across the @checkstack scope. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal @checkstack scoped package; missing description is consistent across the family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped @checkstack package; missing metadata is expected for private org packages, not a spam/malware indicator. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.0.79 | 5 / 3 | |
| 0.0.78 | 5 / 3 | |
| 0.0.77 | 5 / 3 | |
| 0.0.76 | 5 / 3 | |
| 0.0.75 | 5 / 3 | |
| 0.0.74 | 5 / 3 | |
| 0.0.73 | 5 / 3 | |
| 0.0.72 | 5 / 3 | |
| 0.0.71 | 5 / 3 | |
| 0.0.70 | 5 / 3 | |
| 0.0.69 | 5 / 3 | |
| 0.0.68 | 5 / 3 | |
| 0.0.67 | 5 / 3 | |
| 0.0.66 | 5 / 3 | |
| 0.0.65 | 5 / 3 | |
| 0.0.64 | 5 / 3 | |
| 0.0.63 | 5 / 3 | |
| 0.0.62 | 5 / 3 | |
| 0.0.61 | 5 / 3 | |
| 0.0.60 | 5 / 3 | |
| 0.0.59 | 5 / 3 | |
| 0.0.58 | 5 / 3 | |
| 0.0.57 | 5 / 3 | |
| 0.0.56 | 5 / 3 | |
| 0.0.55 | 5 / 3 | |
| 0.0.54 | 5 / 3 | |
| 0.0.53 | 5 / 3 | |
| 0.0.52 | 5 / 3 | |
| 0.0.51 | 5 / 3 | |
| 0.0.50 | 5 / 3 | |
| 0.0.49 | 5 / 3 | |
| 0.0.48 | 5 / 3 | |
| 0.0.47 | 5 / 3 | |
| 0.0.46 | 5 / 3 | |
| 0.0.45 | 5 / 3 | |
| 0.0.44 | 5 / 3 | |
| 0.0.43 | 5 / 3 | |
| 0.0.42 | 5 / 3 | |
| 0.0.41 | 5 / 3 | |
| 0.0.40 | 5 / 3 | |
| 0.0.39 | 5 / 3 | |
| 0.0.38 | 5 / 3 | |
| 0.0.37 | 5 / 3 | |
| 0.0.36 | 5 / 3 | |
| 0.0.35 | 5 / 3 | |
| 0.0.34 | 5 / 3 | |
| 0.0.33 | 5 / 3 | |
| 0.0.32 | 5 / 3 | |
| 0.0.31 | 5 / 3 | |
| 0.0.30 | 5 / 3 | |
| 0.0.29 | 5 / 3 |
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.