@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, 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 |
|---|---|---|---|---|
| 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 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.4.24 | 6 / 5 | |
| 0.4.23 | 6 / 5 | |
| 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 | |
| 0.4.10 | 6 / 5 | |
| 0.4.9 | 6 / 5 | |
| 0.4.8 | 6 / 5 | |
| 0.4.7 | 6 / 5 | |
| 0.4.6 | 6 / 5 | |
| 0.4.5 | 6 / 5 | |
| 0.4.4 | 6 / 5 | |
| 0.4.3 | 6 / 5 | |
| 0.4.2 | 7 / 6 | |
| 0.4.1 | 7 / 6 | |
| 0.4.0 | 7 / 6 | |
| 0.3.8 | 8 / 6 | |
| 0.3.7 | 8 / 6 | |
| 0.3.6 | 8 / 6 | |
| 0.3.5 | 8 / 6 | |
| 0.3.4 | 8 / 6 | |
| 0.3.3 | 8 / 6 | |
| 0.3.2 | 8 / 6 | |
| 0.3.1 | 8 / 6 | |
| 0.3.0 | 8 / 6 | |
| 0.2.16 | 9 / 6 | |
| 0.2.15 | 9 / 6 | |
| 0.2.14 | 9 / 6 | |
| 0.2.13 | 9 / 6 | |
| 0.2.12 | 9 / 6 | |
| 0.2.11 | 9 / 6 | |
| 0.2.10 | 9 / 6 | |
| 0.2.9 | 9 / 6 | |
| 0.2.8 | 9 / 6 | |
| 0.2.7 | 9 / 6 | |
| 0.2.6 | 9 / 6 | |
| 0.2.5 | 9 / 6 | |
| 0.2.4 | 9 / 6 | |
| 0.2.3 | 9 / 6 | |
| 0.2.2 | 9 / 6 | |
| 0.2.1 | 9 / 6 | |
| 0.2.0 | 9 / 6 |
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
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.3.4
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.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.