@backstage/plugin-catalog-backend-module-github-org
The github-org backend module for the catalog plugin.
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 |
|---|---|---|---|---|
| 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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.