@backstage/plugin-events-backend-module-gitlab
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo plugin; missing description is a known pattern for this package family, not a malicious signal. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage plugin with 1,257 days of history and 5.1k weekly downloads; lack of provenance is not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.12 | 3 / 3 | |
| 0.3.11 | 3 / 3 | |
| 0.3.10 | 3 / 3 | |
| 0.3.9 | 3 / 3 | |
| 0.3.8 | 3 / 3 | |
| 0.3.7 | 3 / 3 | |
| 0.3.6 | 3 / 3 | |
| 0.3.5 | 3 / 3 | |
| 0.3.4 | 3 / 3 | |
| 0.3.3 | 3 / 3 | |
| 0.3.2 | 3 / 3 | |
| 0.3.1 | 3 / 3 |
v0.3.12
1 finding[Accepted risk] Package 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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.