A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 9.6 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
79.8
12,326 stars · license n/a
Metabase versus react-native-firebase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; react-native-firebase is written mainly in TypeScript. The composite score is 89.4 for Metabase and 79.8 for react-native-firebase.
Metabase has 50,382 GitHub stars to react-native-firebase's 12,326, a gap of 38,056 (4.09×). Forks are 7,016 for Metabase and 2,332 for react-native-firebase. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 88.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and react-native-firebase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 57 for react-native-firebase (0.005 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. react-native-firebase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 52 for Metabase and 30 for react-native-firebase. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). react-native-firebase is not (12,326 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Metabase is freemium, react-native-firebase is unpriced in this catalog.
The lead is split. Metabase is furthest ahead on self-hosting (100 to 35), while react-native-firebase is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against react-native-firebase at 79.8, a 9.6 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Metabase | react-native-firebase |
|---|---|---|
| GitHub stars | 50,382 | 12,326 |
| Forks | 7,016 | 2,332 |
| Open issues | 4,696 | 57 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 52 | 96 |
| License | 52 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 89.4 | 79.8 |
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
🔥 A well-tested feature-rich modular Firebase implementation for React Native. Supports both iOS & Android platforms for all Firebase services.
Metabase has more GitHub stars: 50,382 versus 12,326 for react-native-firebase. The gap is 38,056 stars.
Both were last pushed on 17 November 2026.
Only Metabase is marked self-hostable. react-native-firebase is not.
Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. react-native-firebase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and react-native-firebase scores 79.8. This page calls that a clear lead for Metabase.