@backstage/plugin-events-backend-module-google-pubsub
The google-pubsub backend module for the events plugin.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/filter-predicates | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-events-node | AI (dependencies): Official @backstage/* package in the canonical Backstage monorepo; unvetted status is a registry gap, not a real risk. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Common in Backstage monorepo packages; may be used in type declarations or transitively. Same org scope, no risk. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Common in Backstage monorepo packages; may be used in config schema declarations. Same org scope, no risk. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 7 / 5 | |
| 0.2.2 | 7 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 | |
| 0.1.7 | 7 / 5 | |
| 0.1.6 | 7 / 5 | |
| 0.1.5 | 7 / 5 | |
| 0.1.4 | 7 / 5 | |
| 0.1.3 | 7 / 5 | |
| 0.1.2 | 7 / 5 | |
| 0.1.1 | 7 / 5 | |
| 0.1.0 | 7 / 5 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.