@backstage/plugin-catalog-backend-module-openapi
A Backstage catalog backend module that helps with OpenAPI specifications
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/types | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/integration | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): Sibling package from the official Backstage monorepo; expected dependency for all @backstage/* plugins. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1400+ days history and 13.5k weekly downloads; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 69 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.2.24 | 8 / 3 | |
| 0.2.23 | 8 / 3 | |
| 0.2.22 | 8 / 3 | |
| 0.2.21 | 8 / 3 | |
| 0.2.20 | 8 / 3 | |
| 0.2.19 | 8 / 3 | |
| 0.2.18 | 8 / 3 | |
| 0.2.17 | 8 / 3 | |
| 0.2.16 | 8 / 3 | |
| 0.2.15 | 8 / 3 | |
| 0.2.14 | 8 / 3 | |
| 0.2.13 | 8 / 3 | |
| 0.2.12 | 8 / 3 | |
| 0.2.11 | 8 / 3 | |
| 0.2.10 | 8 / 3 | |
| 0.2.9 | 8 / 3 | |
| 0.2.8 | 8 / 3 | |
| 0.2.7 | 8 / 3 | |
| 0.2.6 | 8 / 3 | |
| 0.2.5 | 12 / 3 | |
| 0.2.4 | 12 / 3 | |
| 0.2.3 | 12 / 3 | |
| 0.2.2 | 12 / 3 | |
| 0.2.1 | 12 / 3 | |
| 0.2.0 | 12 / 3 | |
| 0.1.43 | 12 / 3 | |
| 0.1.42 | 12 / 3 | |
| 0.1.41 | 12 / 3 | |
| 0.1.40 | 12 / 3 | |
| 0.1.39 | 12 / 3 | |
| 0.1.38 | 12 / 3 | |
| 0.1.37 | 12 / 3 | |
| 0.1.36 | 12 / 3 | |
| 0.1.35 | 12 / 3 | |
| 0.1.34 | 12 / 3 | |
| 0.1.33 | 12 / 3 | |
| 0.1.32 | 12 / 3 | |
| 0.1.31 | 12 / 3 | |
| 0.1.30 | 12 / 3 | |
| 0.1.29 | 12 / 3 | |
| 0.1.28 | 12 / 3 | |
| 0.1.27 | 12 / 3 | |
| 0.1.26 | 12 / 3 | |
| 0.1.25 | 11 / 3 | |
| 0.1.24 | 11 / 3 | |
| 0.1.23 | 11 / 3 | |
| 0.1.22 | 11 / 3 | |
| 0.1.21 | 11 / 3 | |
| 0.1.20 | 11 / 3 | |
| 0.1.19 | 11 / 3 | |
| 0.1.18 | 11 / 3 | |
| 0.1.17 | 11 / 3 | |
| 0.1.16 | 11 / 3 | |
| 0.1.15 | 11 / 3 | |
| 0.1.14 | 11 / 3 | |
| 0.1.13 | 11 / 3 | |
| 0.1.12 | 11 / 3 | |
| 0.1.11 | 11 / 3 | |
| 0.1.10 | 11 / 3 | |
| 0.1.9 | 10 / 3 | |
| 0.1.8 | 10 / 3 | |
| 0.1.7 | 10 / 3 | |
| 0.1.6 | 10 / 3 | |
| 0.1.5 | 10 / 3 | |
| 0.1.4 | 10 / 3 | |
| 0.1.3 | 10 / 3 | |
| 0.1.2 | 10 / 3 | |
| 0.1.1 | 10 / 3 | |
| 0.1.0 | 8 / 3 |
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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.43
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
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.36
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.1.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.