@backstage/plugin-events-backend-module-github
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:@octokit/auth-callback | AI (dependencies): @octokit/auth-callback is a legitimate Octokit library for GitHub authentication, appropriate for a GitHub events backend module. Not a risk for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): @backstage/config is used for config schema typing (config.d.ts) in Backstage plugins; not a direct import but legitimately declared. Stable pattern across Backstage plugin packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages commonly omit npm descriptions; not a malware indicator for this well-established package family. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes from a monorepo without Sigstore provenance; consistent across all versions of this package family. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.12 | 9 / 3 | |
| 0.4.11 | 9 / 3 | |
| 0.4.10 | 9 / 3 | |
| 0.4.9 | 9 / 3 | |
| 0.4.8 | 9 / 3 | |
| 0.4.7 | 9 / 3 | |
| 0.4.6 | 9 / 3 | |
| 0.4.5 | 9 / 3 | |
| 0.4.4 | 9 / 3 | |
| 0.4.3 | 9 / 3 | |
| 0.4.2 | 9 / 3 | |
| 0.4.1 | 9 / 3 | |
| 0.4.0 | 9 / 3 |
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.