@message-queue-toolkit/schemas
Useful utilities, interfaces and base classes for message queue handling. Supports AMQP and SQS with a common abstraction on top currently
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 | slsa-provenance | AI (provenance): Package consistently published via CI/CD with Sigstore SLSA attestation; this is the expected publish pattern going forward. | ai | |
| provenance | missing-githead | AI (provenance): CI/CD publish via GitHub Actions with SLSA attestation replaces gitHead; absence is expected for this publish flow. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is consistent with SLSA attestation adoption; repo and maintainer email unchanged. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by CI/CD migration with SLSA attestation; consistent with legitimate project resumption. | ai |
v7.2.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.