@backstage/plugin-auth-backend-module-google-provider
A Google auth provider module for the Backstage auth backend
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:passport-google-oauth20 | AI (dependencies): passport-google-oauth20 is a well-known, widely-used OAuth2 Passport strategy; its use in a Google auth provider plugin is expected and appropriate. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo publishes hundreds of packages without Sigstore provenance; this is a stable characteristic of the project's release pipeline, not a risk indicator. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.3.17 | 5 / 6 | |
| 0.3.16 | 5 / 6 | |
| 0.3.15 | 5 / 6 | |
| 0.3.14 | 5 / 6 | |
| 0.3.13 | 5 / 6 | |
| 0.3.12 | 5 / 6 | |
| 0.3.11 | 5 / 6 | |
| 0.3.10 | 5 / 6 | |
| 0.3.9 | 5 / 6 | |
| 0.3.8 | 5 / 6 | |
| 0.3.7 | 5 / 6 | |
| 0.3.6 | 5 / 6 | |
| 0.3.5 | 5 / 6 | |
| 0.3.4 | 5 / 6 | |
| 0.3.3 | 5 / 6 | |
| 0.3.2 | 4 / 6 | |
| 0.3.1 | 4 / 6 | |
| 0.3.0 | 4 / 6 | |
| 0.2.4 | 4 / 5 | |
| 0.2.3 | 4 / 5 | |
| 0.2.2 | 4 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.21 | 4 / 5 | |
| 0.1.20 | 4 / 5 | |
| 0.1.19 | 4 / 5 | |
| 0.1.18 | 4 / 5 | |
| 0.1.17 | 4 / 5 | |
| 0.1.16 | 4 / 5 | |
| 0.1.15 | 4 / 5 | |
| 0.1.14 | 4 / 5 | |
| 0.1.13 | 4 / 5 | |
| 0.1.12 | 4 / 5 | |
| 0.1.11 | 4 / 5 | |
| 0.1.10 | 4 / 5 | |
| 0.1.9 | 4 / 5 | |
| 0.1.8 | 4 / 5 | |
| 0.1.7 | 4 / 5 | |
| 0.1.6 | 4 / 5 | |
| 0.1.5 | 4 / 6 | |
| 0.1.4 | 4 / 6 | |
| 0.1.3 | 4 / 6 | |
| 0.1.2 | 4 / 6 | |
| 0.1.1 | 4 / 6 | |
| 0.1.0 | 4 / 6 |
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
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.1.15
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.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.