← Home

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

A Backstage catalog backend module that helps integrate towards GitHub

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
publish-pattern new-deps-added AI (publish-pattern): New deps are all official Backstage/Octokit packages, consistent with a GitHub integration plugin. No malicious signal. ai
dependencies unvetted-dep:@backstage/types AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@backstage/config AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@backstage/errors AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@backstage/integration AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@octokit/auth-callback AI (dependencies): Official @octokit/* package from GitHub; legitimate dependency for GitHub API auth. ai
dependencies unvetted-dep:@octokit/webhooks-types AI (dependencies): Official @octokit/* package from GitHub; legitimate type dependency. ai
dependencies unvetted-dep:@backstage/catalog-model AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:octokit AI (dependencies): octokit is GitHub's official SDK; legitimate dependency for a GitHub integration plugin. ai
dependencies unvetted-dep:@backstage/plugin-events-node AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@backstage/plugin-catalog-node AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:@backstage/plugin-catalog-common AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
phantom-deps phantom-dep:@octokit/webhooks-types AI (phantom-deps): Type-only usage in config files is expected for webhook type definitions; not a real phantom dep concern. ai
phantom-deps phantom-dep:@backstage/plugin-catalog-common AI (phantom-deps): Same org scope package; indirect usage within the Backstage monorepo ecosystem is expected. ai
provenance no-provenance AI (provenance): Established Backstage monorepo package with 1500+ days history; lack of provenance is common and not a risk signal here. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai

Versions (showing 13 of 13)

Version Deps Published
0.13.2 20 / 9
0.13.1 21 / 9
0.13.0 20 / 10
0.12.2 20 / 10
0.12.1 15 / 5
0.12.0 15 / 5
0.11.2 15 / 5
0.11.1 15 / 5
0.11.0 17 / 6
0.10.2 17 / 5
0.10.1 17 / 5
0.10.0 17 / 5
0.9.0 17 / 5

v0.13.2

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.13.1

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.11.1

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.11.0

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.10.2

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.10.1

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.10.0

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.

v0.9.0

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.