@backstage/plugin-scaffolder-backend-module-azure
The azure module for @backstage/plugin-scaffolder-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:azure-devops-node-api | AI (dependencies): azure-devops-node-api is the canonical Microsoft SDK for Azure DevOps; its use is expected and appropriate for this Azure scaffolder plugin. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core Backstage framework dependency; expected for all Backstage backend plugin modules. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-scaffolder-node | AI (dependencies): Core Backstage scaffolder node dependency; expected for all scaffolder backend modules. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes hundreds of packages via automated pipelines without Sigstore provenance; absence is consistent across the entire @backstage scope. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.21 | 7 / 2 | |
| 0.2.20 | 7 / 2 | |
| 0.2.19 | 7 / 2 | |
| 0.2.18 | 7 / 2 | |
| 0.2.17 | 7 / 2 | |
| 0.2.16 | 7 / 2 | |
| 0.2.15 | 7 / 2 | |
| 0.2.14 | 7 / 2 | |
| 0.2.13 | 7 / 2 | |
| 0.2.12 | 7 / 2 | |
| 0.2.11 | 7 / 2 | |
| 0.2.10 | 7 / 2 | |
| 0.2.9 | 7 / 2 |
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.19
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.18
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.17
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.16
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.15
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.