@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 — 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 |
|---|---|---|---|---|
| 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 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 0.0.28 | 5 / 3 | |
| 0.0.26 | 5 / 3 | |
| 0.0.21 | 5 / 3 | |
| 0.0.18 | 5 / 3 | |
| 0.0.17 | 5 / 3 | |
| 0.0.16 | 5 / 3 | |
| 0.0.15 | 5 / 3 | |
| 0.0.14 | 5 / 3 | |
| 0.0.13 | 5 / 3 | |
| 0.0.11 | 5 / 3 | |
| 0.0.10 | 5 / 3 | |
| 0.0.9 | 5 / 3 | |
| 0.0.6 | 5 / 3 | |
| 0.0.5 | 5 / 3 | |
| 0.0.4 | 5 / 3 | |
| 0.0.2 | 5 / 3 |
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.