@checkstack/queue-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent across all versions. | ai | |
| provenance | missing-githead | AI (provenance): Org-internal package with 30 versions; no other supply-chain indicators; likely CI environment change. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Monorepo workspace package; deps may be used transitively or in config files. | ai | |
| phantom-deps | phantom-dep:@checkstack/common | AI (phantom-deps): Same-org workspace dependency; phantom detection is a false positive in monorepo context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for org-scoped private packages. | ai | |
| phantom-deps | phantom-dep:@checkstack/queue-api | AI (phantom-deps): Same-org workspace dependency; phantom detection is a false positive in monorepo context. | ai | |
| phantom-deps | phantom-dep:@hono/zod-validator | AI (phantom-deps): Monorepo workspace package; deps may be used transitively or in config files. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Monorepo workspace package; deps may be used transitively or in config files. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 8 / 3 | |
| 0.4.3 | 8 / 3 | |
| 0.4.2 | 8 / 3 | |
| 0.4.1 | 8 / 3 | |
| 0.4.0 | 8 / 3 | |
| 0.3.8 | 8 / 3 | |
| 0.3.7 | 8 / 3 | |
| 0.3.6 | 8 / 3 | |
| 0.3.5 | 8 / 3 | |
| 0.3.4 | 8 / 3 | |
| 0.3.3 | 8 / 3 | |
| 0.3.2 | 8 / 3 | |
| 0.3.1 | 8 / 3 | |
| 0.2.22 | 8 / 3 | |
| 0.2.21 | 8 / 3 | |
| 0.2.1 | 7 / 4 | |
| 0.0.3 | 7 / 4 |
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.3.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.3.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.