@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, so a manually published version cannot be tied back to a reviewed commit.
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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.3.14 | 3 / 3 | |
| 0.3.13 | 3 / 3 | |
| 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 | |
| 0.3.0 | 3 / 3 | |
| 0.2.18 | 3 / 3 | |
| 0.2.17 | 3 / 3 | |
| 0.2.16 | 3 / 3 | |
| 0.2.15 | 3 / 3 | |
| 0.2.14 | 3 / 3 | |
| 0.2.13 | 3 / 3 | |
| 0.2.12 | 3 / 3 | |
| 0.2.11 | 3 / 3 | |
| 0.2.10 | 3 / 3 | |
| 0.2.9 | 3 / 3 | |
| 0.2.8 | 3 / 3 | |
| 0.2.7 | 3 / 3 | |
| 0.2.6 | 3 / 3 | |
| 0.2.5 | 3 / 3 | |
| 0.2.4 | 3 / 3 | |
| 0.2.3 | 3 / 3 | |
| 0.2.2 | 3 / 3 | |
| 0.2.1 | 3 / 3 | |
| 0.2.0 | 3 / 3 |
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.2.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.