← Home

@backstage/plugin-scaffolder-backend-module-gitlab

14
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 14 of 14)

Version Deps Published
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

v0.11.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.