@backstage/plugin-auth-backend-module-cloudflare-access-provider
The cloudflare-access-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, so a manually published version cannot be tied back to a reviewed commit.
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): Monorepo sub-packages in the Backstage project routinely lack standalone keywords and detailed READMEs; documentation lives in the main repo. Not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages are published without Sigstore provenance; this is consistent across all versions and not a security concern for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.4.17 | 7 / 7 | |
| 0.4.16 | 7 / 7 | |
| 0.4.15 | 7 / 7 | |
| 0.4.14 | 7 / 8 | |
| 0.4.13 | 7 / 8 | |
| 0.4.12 | 7 / 8 | |
| 0.4.11 | 7 / 8 | |
| 0.4.10 | 7 / 8 | |
| 0.4.9 | 7 / 8 | |
| 0.4.8 | 7 / 8 | |
| 0.4.7 | 7 / 8 | |
| 0.4.6 | 7 / 8 | |
| 0.4.5 | 7 / 8 | |
| 0.4.4 | 7 / 8 | |
| 0.4.3 | 7 / 8 | |
| 0.4.2 | 6 / 8 | |
| 0.4.1 | 6 / 8 | |
| 0.4.0 | 6 / 8 | |
| 0.3.4 | 6 / 8 | |
| 0.3.3 | 6 / 8 | |
| 0.3.2 | 7 / 8 | |
| 0.3.1 | 7 / 8 | |
| 0.3.0 | 7 / 8 | |
| 0.2.1 | 7 / 8 | |
| 0.2.0 | 7 / 8 | |
| 0.1.5 | 7 / 8 | |
| 0.1.4 | 7 / 8 | |
| 0.1.3 | 7 / 8 | |
| 0.1.2 | 7 / 8 | |
| 0.1.1 | 7 / 8 |
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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.