@firebase/database-compat
The Realtime Database component of the Firebase JS SDK.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): google-wombot is Google's trusted automation publisher; dormancy in a compat package is expected as Firebase SDK evolves. No material changes in this version diff. | ai | |
| provenance | publisher-changed | AI (provenance): google-wombot is Google's known Firebase publishing automation account; the transition from individual maintainers to this bot is a documented, ecosystem-wide pattern across all Firebase npm packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal is consistent with Google's consolidation of Firebase publishing under the google-wombot automation account; not indicative of a takeover. | ai | |
| dependencies | unvetted-dep:@firebase/database-types | AI (dependencies): First-party Firebase package; expected dependency for @firebase/database-compat. | ai | |
| dependencies | unvetted-dep:@firebase/database | AI (dependencies): First-party Firebase package; expected dependency for @firebase/database-compat. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper commonly used as an implicit dependency in TypeScript-compiled Firebase packages; stable false positive. | ai | |
| dependencies | unvetted-dep:@firebase/util | AI (dependencies): First-party Firebase package; expected dependency for @firebase/database-compat. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is an internal Firebase SDK compat sub-package in a monorepo; sparse README and no keywords are expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Firebase SDK packages published by google-wombot predate Sigstore provenance adoption; absence is expected and consistent across all versions. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.1.4 | 6 / 2 | |
| 2.1.3 | 6 / 2 | |
| 2.1.2 | 6 / 2 | |
| 2.1.1 | 6 / 2 | |
| 2.1.0 | 6 / 2 | |
| 2.0.11 | 6 / 2 | |
| 2.0.10 | 6 / 2 | |
| 2.0.9 | 6 / 2 | |
| 2.0.8 | 6 / 2 | |
| 2.0.7 | 6 / 2 | |
| 2.0.6 | 6 / 2 | |
| 2.0.5 | 6 / 2 | |
| 2.0.4 | 6 / 2 | |
| 2.0.3 | 6 / 2 | |
| 2.0.2 | 6 / 2 | |
| 2.0.1 | 6 / 2 | |
| 2.0.0 | 6 / 2 | |
| 1.0.9 | 6 / 2 | |
| 1.0.8 | 6 / 2 | |
| 1.0.7 | 6 / 2 | |
| 1.0.6 | 6 / 2 | |
| 1.0.5 | 6 / 2 | |
| 1.0.4 | 6 / 2 | |
| 1.0.3 | 6 / 2 | |
| 1.0.2 | 6 / 2 | |
| 1.0.1 | 6 / 2 | |
| 1.0.0 | 6 / 2 | |
| 0.3.4 | 6 / 2 | |
| 0.3.3 | 6 / 2 | |
| 0.3.2 | 6 / 2 | |
| 0.3.1 | 6 / 2 | |
| 0.3.0 | 6 / 2 | |
| 0.2.10 | 6 / 1 | |
| 0.2.9 | 6 / 1 | |
| 0.2.8 | 6 / 1 | |
| 0.2.7 | 6 / 1 | |
| 0.2.6 | 6 / 1 | |
| 0.2.5 | 6 / 1 | |
| 0.2.4 | 6 / 1 | |
| 0.2.3 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.8 | 6 / 1 | |
| 0.1.7 | 6 / 1 | |
| 0.1.6 | 6 / 1 | |
| 0.1.5 | 6 / 1 | |
| 0.1.4 | 6 / 1 | |
| 0.1.3 | 6 / 1 | |
| 0.1.2 | 6 / 1 | |
| 0.1.1 | 6 / 1 |
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsThis version was published by a different npm account than previous versions on 2023-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsThis version was published by a different npm account than previous versions on 2023-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version was published by a different npm account than previous versions on 2023-01-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2022-12-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
2 findingsThis version was published by a different npm account than previous versions on 2022-10-27. This could indicate a legitimate maintainer transition or an account compromise.
[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
2 findingsThis version was published by a different npm account than previous versions on 2022-09-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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 2022-08-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.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 2022-08-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.3
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 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.2
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 2022-06-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.1
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 2022-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
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.3
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.2
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.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.