A
football_analytics
53.9
2,859 stars · license n/a
Analytics
Metabase leads by 35.5 · decisive
A
53.9
2,859 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
football_analytics versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. football_analytics is written mainly in Jupyter Notebook; Metabase is written mainly in Clojure. The composite score is 53.9 for football_analytics and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to football_analytics's 2,859, a gap of 47,523 (17.62×). Forks are 376 for football_analytics and 7,016 for Metabase. On the log scale used inside this pair, adoption is 74 versus 100, and the fork community is 67 versus 100.
Push history: football_analytics was last pushed on 09 October 2025 (404 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 14 for football_analytics (0.005 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 16 and 100.
football_analytics 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. 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. License scores in this pair are 30 for football_analytics and 52 for Metabase. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). football_analytics is not (2,859 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: football_analytics is unpriced in this catalog, Metabase is freemium.
The lead is split. football_analytics is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against football_analytics at 53.9, a 35.5 point decisive 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 | football_analytics | Metabase |
|---|---|---|
| GitHub stars | 2,859 | 50,382 |
| Forks | 376 | 7,016 |
| Open issues | 14 | 4,696 |
| Adoption | 74 | 100 |
| Activity | 16 | 100 |
| Community | 67 | 100 |
| Issue health | 96 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 53.9 | 89.4 |
📊⚽ A collection of football analytics projects, data, and analysis by Edd Webster (@eddwebster), including a curated list of publicly available resources published by the football analytics community.
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.
Metabase has more GitHub stars: 50,382 versus 2,859 for football_analytics. The gap is 47,523 stars.
Metabase was pushed more recently: 17 November 2026 versus 09 October 2025 for football_analytics. That is 404 days apart.
Only Metabase is marked self-hostable. football_analytics is not.
football_analytics 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and football_analytics scores 53.9. This page calls that a decisive lead for Metabase.