@backstage/plugin-events-backend-module-aws-sqs
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): Backstage monorepo package with clear role/purpose in package.json; missing description is benign for this context. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is uncommon across npm; not a signal for this established Backstage plugin. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-sqs | AI (dependencies): Official AWS SDK v3 package from Amazon; well-known, widely used, no malicious signals. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official Backstage monorepo package; legitimate well-known dependency stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-events-node | AI (dependencies): Official Backstage monorepo package; legitimate well-known dependency stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo package; legitimate well-known dependency stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official Backstage monorepo package; legitimate well-known dependency stable across all versions of this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.4.22 | 6 / 5 | |
| 0.4.21 | 6 / 5 | |
| 0.4.20 | 6 / 5 | |
| 0.4.19 | 6 / 5 | |
| 0.4.18 | 6 / 5 | |
| 0.4.17 | 6 / 5 | |
| 0.4.16 | 6 / 5 | |
| 0.4.15 | 6 / 5 | |
| 0.4.14 | 6 / 5 | |
| 0.4.13 | 6 / 5 | |
| 0.4.12 | 6 / 5 | |
| 0.4.11 | 6 / 5 |
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.