@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, 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): 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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.2.33 | 3 / 5 | |
| 0.2.32 | 2 / 3 | |
| 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 | |
| 0.2.19 | 2 / 3 | |
| 0.2.18 | 2 / 3 | |
| 0.2.17 | 2 / 3 | |
| 0.2.16 | 2 / 3 | |
| 0.2.15 | 2 / 3 | |
| 0.2.14 | 2 / 3 | |
| 0.2.13 | 2 / 3 | |
| 0.2.12 | 2 / 3 | |
| 0.2.11 | 2 / 3 | |
| 0.2.10 | 2 / 3 | |
| 0.2.9 | 2 / 3 | |
| 0.2.8 | 2 / 3 | |
| 0.2.7 | 2 / 3 | |
| 0.2.6 | 2 / 3 | |
| 0.2.5 | 2 / 3 | |
| 0.2.4 | 2 / 3 | |
| 0.2.3 | 2 / 3 | |
| 0.2.2 | 2 / 3 | |
| 0.2.1 | 2 / 3 | |
| 0.2.0 | 2 / 3 |
v0.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.