@backstage/plugin-auth-backend-module-gitlab-provider
The gitlab-provider backend module for the auth plugin.
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:passport-gitlab2 | AI (dependencies): passport-gitlab2 is the standard Passport.js strategy for GitLab OAuth; expected dependency for this auth provider module. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): First-party Backstage package; expected core dependency for all Backstage auth provider modules. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): First-party Backstage package; expected core dependency for all Backstage backend plugin modules. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is declared as a dependency and used in Backstage auth plugin context; phantom detection is a false positive for this monorepo sub-package pattern. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is a standard peer/direct dep for Passport.js-based auth providers; phantom detection is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and missing keywords are typical for Backstage monorepo sub-packages where docs live in the main repo. Not a spam/malware indicator. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 6 / 6 | |
| 0.4.2 | 6 / 6 | |
| 0.4.1 | 6 / 6 | |
| 0.4.0 | 6 / 6 | |
| 0.3.11 | 6 / 6 | |
| 0.3.10 | 6 / 6 | |
| 0.3.9 | 6 / 6 | |
| 0.3.8 | 6 / 6 | |
| 0.3.7 | 6 / 6 | |
| 0.3.6 | 6 / 6 | |
| 0.3.5 | 6 / 6 | |
| 0.3.4 | 6 / 6 | |
| 0.3.3 | 6 / 6 |
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.