@emartech/rabbitmq-client
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established internal org package; sparse README/keywords are a style choice, not spam. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.12.0 | 5 / 9 | |
| 5.11.0 | 5 / 9 | |
| 5.10.0 | 5 / 9 | |
| 5.9.2 | 5 / 9 | |
| 5.9.1 | 5 / 10 | |
| 5.9.0 | 5 / 11 | |
| 5.8.2 | 5 / 11 | |
| 5.8.1 | 5 / 11 | |
| 5.8.0 | 5 / 11 | |
| 5.7.0 | 5 / 11 | |
| 5.6.0 | 5 / 11 | |
| 5.5.0 | 5 / 11 | |
| 5.4.0 | 5 / 11 |
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.