← Home

@backstage/plugin-catalog-backend-module-openapi

A Backstage catalog backend module that helps with OpenAPI specifications

13
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 13 of 13)

Version Deps Published
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

v0.2.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.14

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.13

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.