@cedarjs/auth-firebase-api
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
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
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 5.0.4 | 1 / 8 | |
| 5.0.3 | 1 / 8 | |
| 5.0.2 | 1 / 8 | |
| 5.0.1 | 1 / 8 | |
| 5.0.0 | 1 / 8 | |
| 4.2.0 | 1 / 9 | |
| 4.1.0 | 1 / 9 | |
| 4.0.0 | 1 / 9 | |
| 3.1.1 | 1 / 9 | |
| 3.1.0 | 1 / 9 | |
| 3.0.0 | 1 / 9 | |
| 2.8.1 | 1 / 9 | |
| 2.8.0 | 1 / 9 | |
| 2.7.0 | 1 / 9 | |
| 2.6.0 | 1 / 9 | |
| 2.5.1 | 1 / 9 | |
| 2.5.0 | 1 / 9 | |
| 2.4.1 | 1 / 9 | |
| 2.4.0 | 1 / 9 | |
| 2.3.0 | 1 / 9 | |
| 2.2.1 | 1 / 9 | |
| 2.2.0 | 1 / 9 | |
| 2.1.1 | 1 / 9 | |
| 2.1.0 | 1 / 9 | |
| 2.0.3 | 1 / 9 | |
| 2.0.2 | 1 / 9 | |
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 9 | |
| 1.1.2 | 1 / 9 | |
| 1.1.1 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.0 | 1 / 9 |
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.