@backstage/plugin-auth-backend-module-oidc-provider
The oidc-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo packages consistently have minimal standalone READMEs and no keywords; this is a structural pattern of the project, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dependency used in Backstage plugin architecture; phantom detection reflects indirect usage pattern common in this ecosystem. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is a declared runtime dependency used in Backstage auth plugin architecture; indirect usage is expected. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency used for config schema validation in Backstage plugins; indirect usage via config files is expected. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-backend | AI (phantom-deps): Same-org Backstage dependency used as a plugin extension point; indirect usage is expected in Backstage module architecture. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.16 | 9 / 9 | |
| 0.4.15 | 9 / 11 | |
| 0.4.14 | 9 / 11 | |
| 0.4.13 | 9 / 11 | |
| 0.4.12 | 9 / 11 | |
| 0.4.11 | 9 / 11 | |
| 0.4.10 | 9 / 11 | |
| 0.4.9 | 9 / 11 | |
| 0.4.8 | 9 / 11 | |
| 0.4.7 | 9 / 11 | |
| 0.4.6 | 9 / 11 | |
| 0.4.5 | 9 / 11 | |
| 0.4.4 | 9 / 11 | |
| 0.4.3 | 9 / 11 |
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.