@backstage/plugin-catalog-backend-module-msgraph
A Backstage catalog backend module that helps integrate towards Microsoft Graph
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
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): Official @backstage/* package from the backstage/backstage monorepo; unvetted status reflects registry gap, not risk. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Official @backstage/* package from the backstage/backstage monorepo; unvetted status reflects registry gap, not risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage/* package from the backstage/backstage monorepo; unvetted status reflects registry gap, not risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official @backstage/* package from the backstage/backstage monorepo; unvetted status reflects registry gap, not risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): Official @backstage/* package from the backstage/backstage monorepo; unvetted status reflects registry gap, not risk. | ai | |
| dependencies | unvetted-dep:@microsoft/microsoft-graph-types | AI (dependencies): Official Microsoft Graph type definitions package; well-known, widely used, no security concern. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo does not currently publish with Sigstore provenance; consistent across all versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 10 / 4 | |
| 0.10.0 | 10 / 4 | |
| 0.9.2 | 11 / 4 | |
| 0.8.2 | 11 / 4 | |
| 0.8.1 | 11 / 4 | |
| 0.8.0 | 11 / 5 | |
| 0.7.3 | 11 / 5 | |
| 0.7.2 | 11 / 5 | |
| 0.7.1 | 11 / 5 | |
| 0.7.0 | 11 / 5 |
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
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.7.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.
v0.7.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.7.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.