@backstage/plugin-auth-backend-module-oauth2-provider
The oauth2-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 sub-packages routinely have short READMEs and no keywords; this is a structural pattern, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is a declared runtime dep used indirectly via passport-oauth2; phantom-dep finding is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages are published without Sigstore provenance; this is consistent across the entire monorepo and not a security concern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.15 | 5 / 6 | |
| 0.4.14 | 5 / 6 | |
| 0.4.13 | 5 / 6 | |
| 0.4.12 | 5 / 6 | |
| 0.4.11 | 5 / 6 | |
| 0.4.10 | 5 / 6 | |
| 0.4.9 | 5 / 6 | |
| 0.4.8 | 5 / 6 | |
| 0.4.7 | 5 / 6 | |
| 0.4.6 | 5 / 6 | |
| 0.4.5 | 5 / 6 | |
| 0.4.4 | 5 / 6 | |
| 0.4.3 | 5 / 6 |
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.