@backstage/plugin-scaffolder-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1100+ days history and 66k+ weekly downloads; lack of provenance is not a risk signal here. | ai | |
| dependencies | unvetted-dep:@gitbeaker/rest | AI (dependencies): @gitbeaker/rest is the official GitLab API client; expected and legitimate dependency for this GitLab scaffolder plugin across all versions. | ai | |
| dependencies | unvetted-dep:@gitbeaker/requester-utils | AI (dependencies): @gitbeaker/requester-utils is part of the official gitbeaker GitLab client suite; expected dependency for this plugin. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package from the official Backstage project; missing description is a cosmetic issue, not a malware signal. | ai | |
| phantom-deps | phantom-dep:@gitbeaker/core | AI (phantom-deps): @gitbeaker/core is a legitimate dependency used indirectly in Backstage plugin config; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@gitbeaker/requester-utils | AI (phantom-deps): @gitbeaker/requester-utils is a legitimate dependency used indirectly in Backstage plugin config; phantom-dep pattern is stable for this package. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.11.8 | 11 / 3 | |
| 0.11.7 | 11 / 3 | |
| 0.11.6 | 11 / 3 | |
| 0.11.5 | 11 / 3 | |
| 0.11.4 | 11 / 3 | |
| 0.11.3 | 10 / 3 | |
| 0.11.2 | 10 / 3 | |
| 0.11.1 | 10 / 3 | |
| 0.11.0 | 10 / 3 | |
| 0.10.0 | 10 / 3 | |
| 0.9.6 | 10 / 3 | |
| 0.9.5 | 11 / 3 | |
| 0.9.4 | 11 / 3 | |
| 0.9.3 | 10 / 3 | |
| 0.9.2 | 10 / 3 | |
| 0.9.1 | 10 / 4 | |
| 0.9.0 | 10 / 4 | |
| 0.8.1 | 10 / 4 | |
| 0.8.0 | 11 / 4 | |
| 0.7.1 | 11 / 4 | |
| 0.7.0 | 11 / 4 | |
| 0.6.2 | 13 / 4 | |
| 0.6.1 | 13 / 4 | |
| 0.6.0 | 13 / 4 | |
| 0.5.1 | 12 / 4 | |
| 0.5.0 | 12 / 4 | |
| 0.4.6 | 12 / 4 | |
| 0.4.5 | 12 / 4 | |
| 0.4.4 | 12 / 4 | |
| 0.4.3 | 12 / 4 | |
| 0.4.2 | 12 / 4 | |
| 0.4.1 | 12 / 4 | |
| 0.4.0 | 12 / 4 | |
| 0.3.3 | 12 / 4 | |
| 0.3.2 | 12 / 5 | |
| 0.3.1 | 12 / 5 | |
| 0.3.0 | 12 / 5 | |
| 0.2.16 | 12 / 4 | |
| 0.2.15 | 12 / 4 | |
| 0.2.14 | 12 / 4 | |
| 0.2.13 | 12 / 4 | |
| 0.2.12 | 10 / 4 | |
| 0.2.11 | 9 / 3 | |
| 0.2.10 | 7 / 3 | |
| 0.2.9 | 6 / 3 | |
| 0.2.8 | 6 / 3 | |
| 0.2.7 | 6 / 3 | |
| 0.2.6 | 6 / 3 | |
| 0.2.5 | 6 / 3 | |
| 0.2.4 | 6 / 3 | |
| 0.2.3 | 6 / 3 | |
| 0.2.2 | 6 / 3 | |
| 0.2.1 | 6 / 3 | |
| 0.2.0 | 6 / 3 | |
| 0.1.0 | 5 / 3 |
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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.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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.