@backstage/plugin-auth-backend-module-gcp-iap-provider
A GCP IAP 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:@backstage/types | AI (dependencies): Official @backstage monorepo sibling package with long history and high downloads; unvetted status reflects pipeline gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage monorepo sibling package with long history and high downloads; unvetted status reflects pipeline gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-auth-node | AI (dependencies): Official @backstage monorepo sibling package with long history and high downloads; unvetted status reflects pipeline gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage monorepo sibling package with long history and high downloads; unvetted status reflects pipeline gap, not actual risk. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages do not currently publish Sigstore provenance; repo URL and package metadata are verifiable and consistent across all versions. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.4.17 | 6 / 3 | |
| 0.4.16 | 6 / 3 | |
| 0.4.15 | 6 / 3 | |
| 0.4.14 | 6 / 3 | |
| 0.4.13 | 6 / 3 | |
| 0.4.12 | 6 / 3 | |
| 0.4.11 | 6 / 3 | |
| 0.4.10 | 6 / 3 | |
| 0.4.9 | 6 / 3 | |
| 0.4.8 | 6 / 3 | |
| 0.4.7 | 6 / 3 | |
| 0.4.6 | 6 / 3 | |
| 0.4.5 | 6 / 3 | |
| 0.4.4 | 6 / 3 | |
| 0.4.3 | 6 / 3 | |
| 0.4.2 | 5 / 3 | |
| 0.4.1 | 5 / 3 | |
| 0.4.0 | 5 / 3 | |
| 0.3.4 | 5 / 3 | |
| 0.3.3 | 5 / 3 | |
| 0.3.2 | 5 / 3 | |
| 0.3.1 | 5 / 3 | |
| 0.3.0 | 5 / 3 | |
| 0.2.19 | 5 / 3 | |
| 0.2.18 | 5 / 3 | |
| 0.2.17 | 5 / 3 | |
| 0.2.16 | 5 / 3 | |
| 0.2.15 | 5 / 3 | |
| 0.2.14 | 5 / 3 | |
| 0.2.13 | 5 / 3 | |
| 0.2.12 | 5 / 3 | |
| 0.2.11 | 5 / 3 | |
| 0.2.10 | 5 / 3 | |
| 0.2.9 | 5 / 3 | |
| 0.2.8 | 5 / 3 | |
| 0.2.7 | 5 / 3 | |
| 0.2.6 | 5 / 3 | |
| 0.2.5 | 5 / 3 | |
| 0.2.4 | 5 / 3 | |
| 0.2.3 | 5 / 3 | |
| 0.2.2 | 5 / 5 | |
| 0.2.1 | 5 / 5 | |
| 0.2.0 | 5 / 5 | |
| 0.1.2 | 5 / 5 | |
| 0.1.1 | 5 / 5 | |
| 0.1.0 | 5 / 5 |
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
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.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
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.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.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.