@amqp-contract/worker
Worker utilities for consuming messages using amqp-contract
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size growth reflects bundled CJS+ESM+type declarations for a growing monorepo package, not injected payload. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-monorepo sibling and a well-known schema spec; consistent with package purpose. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA provenance; CI/CD automation replacing manual publish is expected for this repo. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation confirms CI/CD build integrity; stable positive signal for this package. | ai | |
| dependencies | unvetted-dep:@amqp-contract/core | AI (dependencies): Same monorepo/publisher (@amqp-contract org); sibling package published in lockstep at matching version 0.25.0. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 4 / 14 | |
| 0.23.1 | 4 / 14 | |
| 0.11.0 | 4 / 14 | |
| 0.7.0 | 4 / 14 | |
| 0.3.1 | 4 / 15 | |
| 0.1.4 | 2 / 11 | |
| 0.1.3 | 2 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 | |
| 0.1.0 | 2 / 11 | |
| 0.0.6 | 1 / 11 | |
| 0.0.5 | 1 / 11 | |
| 0.0.4 | 1 / 11 | |
| 0.0.2 | 1 / 9 | |
| 0.0.1 | 1 / 8 |
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. 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.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.