@backstage/plugin-auth-backend-module-onelogin-provider
The onelogin-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-onelogin-oauth | AI (dependencies): passport-onelogin-oauth is an intentional, purpose-appropriate OAuth strategy dependency for this OneLogin auth provider plugin; its use is expected across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo sub-packages consistently have short READMEs and no keywords; documentation lives in the main backstage/backstage repo. Not a spam signal. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared dependency used in type/config context in Backstage auth plugins; phantom detection is a false positive for this monorepo package pattern. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is a declared dependency used transitively in Backstage auth plugins; phantom detection is a false positive for this monorepo package pattern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.15 | 6 / 6 | |
| 0.3.14 | 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.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.