@checkstack/queue-bullmq-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Workspace package; missing description is expected for internal monorepo modules. | 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/queue-api | AI (dependencies): Workspace-scoped internal monorepo dep; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Workspace-scoped internal monorepo dep; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack/* packages; no CI provenance setup in this ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; sparse metadata is expected and not indicative of spam/malware. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.5.11 | 6 / 3 | |
| 0.5.10 | 6 / 3 | |
| 0.5.9 | 6 / 3 | |
| 0.5.8 | 6 / 3 | |
| 0.5.7 | 6 / 4 | |
| 0.5.6 | 6 / 4 | |
| 0.5.5 | 6 / 4 | |
| 0.5.4 | 6 / 4 | |
| 0.5.3 | 6 / 4 | |
| 0.5.2 | 6 / 4 | |
| 0.5.1 | 6 / 4 | |
| 0.5.0 | 6 / 4 | |
| 0.4.16 | 6 / 4 | |
| 0.4.15 | 6 / 4 | |
| 0.4.14 | 6 / 4 | |
| 0.4.13 | 6 / 4 | |
| 0.4.12 | 6 / 4 | |
| 0.4.11 | 6 / 4 | |
| 0.4.10 | 6 / 4 | |
| 0.4.9 | 6 / 4 | |
| 0.4.8 | 6 / 4 | |
| 0.4.7 | 6 / 4 | |
| 0.4.6 | 6 / 4 | |
| 0.4.5 | 6 / 4 | |
| 0.4.4 | 6 / 4 | |
| 0.4.3 | 6 / 4 | |
| 0.4.2 | 6 / 4 | |
| 0.4.1 | 6 / 4 | |
| 0.4.0 | 6 / 4 | |
| 0.3.7 | 6 / 4 | |
| 0.3.6 | 6 / 4 | |
| 0.3.5 | 6 / 4 | |
| 0.3.4 | 6 / 4 | |
| 0.3.3 | 6 / 4 | |
| 0.3.2 | 6 / 4 | |
| 0.3.1 | 6 / 4 | |
| 0.3.0 | 6 / 4 | |
| 0.2.18 | 6 / 4 | |
| 0.2.17 | 6 / 4 | |
| 0.2.16 | 6 / 4 | |
| 0.2.15 | 6 / 4 | |
| 0.2.14 | 6 / 4 | |
| 0.2.13 | 6 / 4 | |
| 0.2.12 | 6 / 4 | |
| 0.2.11 | 6 / 4 | |
| 0.2.10 | 6 / 4 | |
| 0.2.9 | 6 / 4 | |
| 0.2.8 | 6 / 4 | |
| 0.2.7 | 6 / 4 | |
| 0.2.6 | 6 / 4 | |
| 0.2.3 | 6 / 4 |
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.