← Home

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

npm Repository

The github-org backend module for the catalog plugin.

46
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@backstage/config AI (dependencies): Official @backstage/* scoped package from the Backstage monorepo; unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Official @backstage/* scoped package from the Backstage monorepo; unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@backstage/plugin-events-node AI (dependencies): Official @backstage/* scoped package from the Backstage monorepo; unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@backstage/plugin-catalog-node AI (dependencies): Official @backstage/* scoped package from the Backstage monorepo; unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@backstage/plugin-catalog-backend-module-github AI (dependencies): Official @backstage/* scoped package from the Backstage monorepo; unvetted status is a registry gap, not a security concern. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-packages typically have minimal READMEs and no keywords; not indicative of spam or low-value content for this established Backstage plugin. ai
phantom-deps phantom-dep:@backstage/config AI (phantom-deps): Same-org scoped package; phantom dep flag is a minor packaging concern, not a security issue for this established Backstage module. ai

Versions (showing 46 of 46)

Version Deps Published
0.3.24 5 / 2
0.3.23 5 / 2
0.3.22 5 / 2
0.3.21 5 / 2
0.3.20 5 / 2
0.3.19 5 / 2
0.3.18 5 / 2
0.3.17 5 / 2
0.3.16 5 / 2
0.3.15 5 / 2
0.3.14 5 / 3
0.3.13 5 / 3
0.3.12 5 / 3
0.3.11 5 / 3
0.3.10 5 / 3
0.3.9 5 / 3
0.3.8 5 / 3
0.3.7 5 / 3
0.3.6 5 / 3
0.3.5 5 / 3
0.3.4 5 / 3
0.3.3 5 / 3
0.3.2 5 / 3
0.3.1 5 / 3
0.3.0 5 / 3
0.2.2 5 / 3
0.2.1 5 / 3
0.2.0 5 / 3
0.1.17 7 / 3
0.1.16 7 / 3
0.1.15 7 / 3
0.1.14 7 / 3
0.1.13 7 / 3
0.1.12 7 / 3
0.1.11 7 / 3
0.1.10 7 / 3
0.1.9 7 / 3
0.1.8 7 / 3
0.1.7 6 / 3
0.1.6 6 / 3
0.1.5 6 / 3
0.1.4 6 / 3
0.1.3 6 / 3
0.1.2 6 / 3
0.1.1 6 / 3
0.1.0 6 / 3

v0.3.24

1 finding
LOW No provenance attestation provenance

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

v0.3.9

1 finding
LOW No provenance attestation provenance

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

v0.3.8

1 finding
LOW No provenance attestation provenance

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

v0.3.7

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

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

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

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.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.1.0

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.