@checkstack/queue-memory-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): Likely a CI/publish environment change; no other risk signals; publisher has strong track record. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is stable pattern for internal workspace modules. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a recognized license; acceptable for this package. | ai | |
| dependencies | unvetted-dep:@checkstack/queue-api | AI (dependencies): Internal monorepo workspace dependency; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Internal monorepo workspace dependency; not a third-party risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package in @checkstack ecosystem; missing metadata is expected for private/internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack packages; org does not use Sigstore attestation. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.4.35 | 6 / 3 | |
| 0.4.34 | 6 / 3 | |
| 0.4.33 | 6 / 3 | |
| 0.4.32 | 6 / 3 | |
| 0.4.31 | 6 / 3 | |
| 0.4.30 | 6 / 3 | |
| 0.4.29 | 6 / 3 | |
| 0.4.28 | 6 / 3 | |
| 0.4.27 | 6 / 3 | |
| 0.4.26 | 6 / 3 | |
| 0.4.25 | 6 / 3 | |
| 0.4.24 | 6 / 3 | |
| 0.4.23 | 6 / 3 | |
| 0.4.22 | 6 / 3 | |
| 0.4.21 | 6 / 3 | |
| 0.4.20 | 6 / 3 | |
| 0.4.19 | 6 / 3 | |
| 0.4.18 | 6 / 3 | |
| 0.4.17 | 6 / 3 | |
| 0.4.16 | 6 / 3 | |
| 0.4.15 | 6 / 3 | |
| 0.4.14 | 6 / 3 | |
| 0.4.13 | 6 / 3 | |
| 0.4.12 | 6 / 3 | |
| 0.4.11 | 6 / 3 | |
| 0.4.10 | 6 / 3 | |
| 0.4.9 | 6 / 3 | |
| 0.4.8 | 6 / 3 | |
| 0.4.7 | 6 / 3 | |
| 0.4.6 | 6 / 3 | |
| 0.4.5 | 6 / 3 | |
| 0.4.4 | 6 / 3 | |
| 0.4.3 | 6 / 3 | |
| 0.4.2 | 6 / 3 | |
| 0.4.1 | 6 / 3 | |
| 0.4.0 | 6 / 3 | |
| 0.3.18 | 6 / 3 | |
| 0.3.17 | 6 / 3 | |
| 0.3.16 | 6 / 3 | |
| 0.3.15 | 6 / 3 | |
| 0.3.14 | 6 / 3 | |
| 0.3.13 | 6 / 3 | |
| 0.3.12 | 6 / 3 | |
| 0.3.11 | 6 / 3 | |
| 0.3.10 | 6 / 3 | |
| 0.3.9 | 6 / 3 | |
| 0.3.8 | 6 / 3 | |
| 0.3.7 | 6 / 3 | |
| 0.3.6 | 6 / 3 | |
| 0.3.5 | 6 / 3 | |
| 0.3.4 | 6 / 3 |
v0.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.