@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 — 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 |
|---|---|---|---|---|
| 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 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 0.3.3 | 6 / 3 | |
| 0.3.2 | 6 / 3 | |
| 0.3.1 | 6 / 3 | |
| 0.3.0 | 6 / 3 | |
| 0.2.4 | 5 / 3 | |
| 0.2.3 | 5 / 3 | |
| 0.2.2 | 5 / 3 | |
| 0.2.1 | 5 / 3 | |
| 0.2.0 | 5 / 3 | |
| 0.1.0 | 5 / 3 | |
| 0.0.4 | 5 / 3 | |
| 0.0.3 | 5 / 3 | |
| 0.0.2 | 5 / 3 |
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
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.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
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.3.4
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.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
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.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.