@tachybase/plugin-adapter-bullmq
Integrate and manage BullMQ message queues.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent with CI/CD automation for this package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 1.6.24 | 0 / 7 | |
| 1.6.23 | 0 / 7 | |
| 1.6.22 | 0 / 7 | |
| 1.6.21 | 0 / 7 | |
| 1.6.20 | 0 / 7 | |
| 1.6.19 | 0 / 7 | |
| 1.6.18 | 0 / 7 | |
| 1.6.17 | 0 / 7 | |
| 1.6.16 | 0 / 7 | |
| 1.6.15 | 0 / 7 | |
| 1.6.14 | 0 / 7 | |
| 1.6.13 | 0 / 7 | |
| 1.6.12 | 0 / 7 | |
| 1.6.11 | 0 / 7 | |
| 1.6.10 | 0 / 7 | |
| 1.6.9 | 0 / 7 | |
| 1.6.8 | 0 / 7 | |
| 1.6.7 | 0 / 7 | |
| 1.6.6 | 0 / 7 | |
| 1.6.5 | 0 / 7 | |
| 1.6.4 | 0 / 7 | |
| 1.6.3 | 0 / 7 | |
| 1.6.1 | 0 / 7 | |
| 1.6.0 | 0 / 7 | |
| 1.5.1 | 0 / 7 | |
| 1.5.0 | 0 / 7 | |
| 1.4.0 | 0 / 7 | |
| 1.3.25 | 0 / 7 | |
| 1.3.24 | 0 / 7 | |
| 1.3.23 | 0 / 7 | |
| 1.3.22 | 0 / 7 | |
| 1.3.21 | 0 / 3 | |
| 1.3.20 | 0 / 3 | |
| 1.3.19 | 0 / 3 | |
| 1.3.17 | 0 / 3 | |
| 1.3.16 | 0 / 3 | |
| 1.3.15 | 0 / 3 | |
| 1.3.14 | 0 / 3 | |
| 1.3.13 | 0 / 3 | |
| 1.3.12 | 0 / 3 | |
| 1.3.11 | 0 / 3 | |
| 1.3.10 | 0 / 3 | |
| 1.3.9 | 0 / 3 | |
| 1.3.8 | 0 / 3 | |
| 1.3.7 | 0 / 3 | |
| 1.3.6 | 0 / 3 | |
| 1.3.5 | 0 / 3 | |
| 1.3.2 | 0 / 3 | |
| 1.3.1 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.15 | 0 / 3 |
v1.6.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.8
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.