@backstage/plugin-catalog-backend-module-backstage-openapi
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-packages in the @backstage org routinely omit descriptions; not a malware indicator for this established package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): @backstage/config is used indirectly via the Backstage plugin framework; phantom-dep flag is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo publishes without Sigstore provenance; this is consistent across all @backstage/* packages and not a risk signal. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.5.14 | 10 / 2 | |
| 0.5.13 | 11 / 2 | |
| 0.5.12 | 11 / 2 | |
| 0.5.11 | 11 / 2 | |
| 0.5.10 | 11 / 2 | |
| 0.5.9 | 11 / 2 | |
| 0.5.8 | 11 / 2 | |
| 0.5.7 | 11 / 2 | |
| 0.5.6 | 11 / 2 | |
| 0.5.5 | 11 / 2 | |
| 0.5.4 | 11 / 2 | |
| 0.5.3 | 11 / 2 | |
| 0.5.2 | 11 / 2 |
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.5.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.