@backstage/plugin-events-backend
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): Official Backstage monorepo package; missing description is a known pattern in their published packages and not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes from their monorepo CI without Sigstore provenance; consistent across all their packages and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a TypeScript type package listed as a runtime dep for type augmentation; standard pattern in Express-based packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 11 / 8 | |
| 0.6.1 | 11 / 8 | |
| 0.6.0 | 11 / 8 | |
| 0.5.11 | 11 / 8 | |
| 0.5.10 | 11 / 8 | |
| 0.5.9 | 11 / 8 | |
| 0.5.8 | 11 / 8 | |
| 0.5.7 | 11 / 8 | |
| 0.5.6 | 11 / 8 | |
| 0.5.5 | 11 / 8 | |
| 0.5.4 | 11 / 8 | |
| 0.5.3 | 11 / 8 | |
| 0.5.2 | 11 / 8 |
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.