@backstage/plugin-events-backend-module-azure
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 artifact of their build/publish pipeline, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes without Sigstore provenance consistently across its packages; not a risk signal for this well-established project. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.31 | 2 / 3 | |
| 0.2.30 | 2 / 3 | |
| 0.2.29 | 2 / 3 | |
| 0.2.28 | 2 / 3 | |
| 0.2.27 | 2 / 3 | |
| 0.2.26 | 2 / 3 | |
| 0.2.25 | 2 / 3 | |
| 0.2.24 | 2 / 3 | |
| 0.2.23 | 2 / 3 | |
| 0.2.22 | 2 / 3 | |
| 0.2.21 | 2 / 3 | |
| 0.2.20 | 2 / 3 |
v0.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
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.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.