@backstage/plugin-catalog
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/plugin-techdocs-common | AI (dependencies): Official Backstage plugin package from the backstage/backstage monorepo; no security concern. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): Official Material UI icons package, widely used in the React ecosystem; no security concern. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; no security concern. | ai | |
| dependencies | unvetted-dep:zen-observable | AI (dependencies): zen-observable is a legitimate, well-known observable library used throughout the Backstage ecosystem; not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; no security concern. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Official Material UI lab package, widely used in the React ecosystem; no security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package with 1912 versions and 112k weekly downloads; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:history | AI (phantom-deps): history is a declared runtime dependency used in config files; phantom-dep false positive for this package's legitimate usage pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 32 / 16 | |
| 2.0.3 | 32 / 16 | |
| 2.0.2 | 31 / 16 | |
| 1.32.2 | 30 / 16 | |
| 1.32.0 | 30 / 16 |
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.
v2.0.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.
v1.32.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.