@backstage/plugin-catalog-backend-module-azure
A Backstage catalog backend module that helps integrate towards 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/integration | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-events-node | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): First-party Backstage package from the official monorepo; unvetted status reflects registry gap, not actual risk. | ai | |
| phantom-deps | phantom-dep:@azure/identity | AI (phantom-deps): @azure/identity is explicitly declared in dependencies and is a legitimate Azure SDK auth package used by this Azure integration plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established 1500+ day old package with 1479 versions; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.3.19 | 9 / 3 | |
| 0.3.18 | 9 / 3 | |
| 0.3.17 | 9 / 3 | |
| 0.3.16 | 10 / 3 | |
| 0.3.15 | 8 / 3 | |
| 0.3.14 | 8 / 3 | |
| 0.3.13 | 8 / 3 | |
| 0.3.12 | 8 / 3 | |
| 0.3.11 | 8 / 3 | |
| 0.3.10 | 8 / 3 | |
| 0.3.9 | 8 / 4 | |
| 0.3.8 | 8 / 4 | |
| 0.3.7 | 8 / 4 | |
| 0.3.6 | 8 / 4 | |
| 0.3.5 | 8 / 4 | |
| 0.3.4 | 8 / 4 | |
| 0.3.3 | 8 / 4 | |
| 0.3.2 | 8 / 4 | |
| 0.3.1 | 8 / 4 | |
| 0.3.0 | 8 / 4 | |
| 0.2.4 | 7 / 4 | |
| 0.2.3 | 7 / 4 | |
| 0.2.2 | 7 / 4 | |
| 0.2.1 | 7 / 4 | |
| 0.2.0 | 7 / 4 | |
| 0.1.42 | 9 / 4 | |
| 0.1.41 | 9 / 4 | |
| 0.1.40 | 9 / 4 | |
| 0.1.39 | 9 / 4 | |
| 0.1.38 | 9 / 4 | |
| 0.1.37 | 9 / 4 | |
| 0.1.36 | 10 / 4 | |
| 0.1.35 | 10 / 4 | |
| 0.1.34 | 10 / 4 | |
| 0.1.33 | 10 / 4 | |
| 0.1.32 | 10 / 4 | |
| 0.1.31 | 10 / 4 | |
| 0.1.30 | 10 / 4 | |
| 0.1.29 | 10 / 4 | |
| 0.1.28 | 10 / 4 |
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
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.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
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.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.