@backstage/plugin-auth-backend-module-okta-provider
The okta-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:@davidzemon/passport-okta-oauth | AI (dependencies): Intentional dependency by the Backstage project for Okta OAuth passport strategy; present across multiple versions of this well-governed CNCF package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is declared as a dependency for compatibility in this Backstage backend plugin module; phantom-dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is declared as a dependency for compatibility in this Backstage auth plugin module; phantom-dep finding is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 886 days history and 31.6k weekly downloads; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.15 | 6 / 6 | |
| 0.2.14 | 6 / 6 | |
| 0.2.13 | 6 / 6 | |
| 0.2.12 | 6 / 6 | |
| 0.2.11 | 6 / 6 | |
| 0.2.10 | 6 / 6 | |
| 0.2.9 | 6 / 6 | |
| 0.2.8 | 6 / 6 | |
| 0.2.7 | 6 / 6 | |
| 0.2.6 | 6 / 6 | |
| 0.2.5 | 6 / 6 | |
| 0.2.4 | 6 / 6 | |
| 0.2.3 | 6 / 6 |
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.