@backstage/plugin-catalog-import
A Backstage plugin the helps you import entities into your 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Monorepo pattern; same-org dependency managed at workspace level. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Backstage plugins intentionally pin @material-ui/[email protected] as a known MUI v4 lab dependency. This is a stable, widely-used package in the Backstage ecosystem, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): @backstage/config is a same-org peer used for config schema typing; phantom detection is a false positive for this Backstage plugin pattern. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes from its monorepo CI without Sigstore provenance; this is consistent across all @backstage/* packages and not a risk signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.13.13 | 23 / 14 | |
| 0.13.12 | 23 / 14 | |
| 0.13.11 | 22 / 14 | |
| 0.13.10 | 22 / 14 | |
| 0.13.9 | 22 / 14 | |
| 0.13.8 | 22 / 14 | |
| 0.13.7 | 23 / 14 | |
| 0.13.6 | 22 / 14 | |
| 0.13.5 | 22 / 14 | |
| 0.13.2 | 22 / 14 | |
| 0.13.1 | 22 / 14 | |
| 0.13.0 | 22 / 14 |
v0.13.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
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.13.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.13.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.13.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.13.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.