@firebase/auth-compat
FirebaseAuth compatibility package that uses API style compatible with Firebase@8 and prior versions
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Firebase auth-compat is a large SDK compatibility package with multiple build output formats; adding source files across versions is normal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): undici is a well-known Node.js HTTP client maintained by the Node.js team; this is a legitimate swap from node-fetch to undici, a common modernization pattern for Firebase SDK packages. | ai | |
| provenance | publisher-changed | AI (provenance): chholland is a long-standing Firebase/Google publisher (2677 days, 1044 approved packages). The transition from feiyang.chen reflects a legitimate internal Firebase team handoff, not a compromise. | ai | |
| phantom-deps | phantom-dep:selenium-webdriver | AI (phantom-deps): selenium-webdriver is used in webdriver integration tests within this monorepo package; its presence in dependencies is a packaging quirk, not a security concern. | ai | |
| dependencies | unvetted-dep:undici | AI (dependencies): undici is a well-known HTTP client used legitimately by Firebase Auth for Node.js HTTP operations; stable and expected dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Firebase packages published via google-wombot do not currently include Sigstore provenance; this is consistent across the entire Firebase JS SDK release pipeline. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; its use as an implicit dependency is a well-known pattern in Firebase/TypeScript packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Firebase SDK sub-packages routinely lack keywords and detailed READMEs; documentation lives in the parent SDK. Not a spam indicator for this package. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 0.6.6 | 5 / 7 | |
| 0.6.5 | 5 / 7 | |
| 0.6.4 | 5 / 7 | |
| 0.6.3 | 5 / 7 | |
| 0.6.2 | 5 / 7 | |
| 0.6.1 | 5 / 7 | |
| 0.6.0 | 5 / 7 | |
| 0.5.28 | 5 / 7 | |
| 0.5.27 | 5 / 7 | |
| 0.5.26 | 5 / 7 | |
| 0.5.25 | 5 / 7 | |
| 0.5.24 | 5 / 7 | |
| 0.5.23 | 5 / 7 | |
| 0.5.22 | 5 / 7 | |
| 0.5.21 | 5 / 7 | |
| 0.5.20 | 5 / 7 | |
| 0.5.19 | 5 / 7 | |
| 0.5.18 | 5 / 7 | |
| 0.5.17 | 5 / 7 | |
| 0.5.16 | 5 / 7 | |
| 0.5.15 | 5 / 7 | |
| 0.5.14 | 6 / 7 | |
| 0.5.13 | 6 / 7 | |
| 0.5.12 | 6 / 7 | |
| 0.5.11 | 6 / 7 | |
| 0.5.10 | 6 / 7 | |
| 0.5.9 | 6 / 7 | |
| 0.5.8 | 6 / 7 | |
| 0.5.7 | 6 / 7 | |
| 0.5.6 | 6 / 7 | |
| 0.5.5 | 6 / 7 | |
| 0.5.4 | 6 / 7 | |
| 0.5.3 | 6 / 7 | |
| 0.5.2 | 6 / 7 | |
| 0.5.1 | 6 / 7 | |
| 0.5.0 | 6 / 7 | |
| 0.4.9 | 6 / 7 | |
| 0.4.8 | 6 / 7 | |
| 0.4.7 | 6 / 7 | |
| 0.4.6 | 6 / 7 | |
| 0.4.5 | 6 / 7 | |
| 0.4.4 | 6 / 7 | |
| 0.4.3 | 6 / 7 | |
| 0.4.2 | 6 / 7 | |
| 0.4.1 | 6 / 7 | |
| 0.4.0 | 6 / 7 | |
| 0.3.7 | 6 / 7 | |
| 0.3.6 | 6 / 7 | |
| 0.3.5 | 6 / 7 | |
| 0.3.4 | 6 / 7 | |
| 0.3.3 | 6 / 7 |
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.