A
django-DefectDojo
85.7
5,244 stars · BSD-3-Clause
Analytics
Metabase leads by 3.7 · narrow
A
85.7
5,244 stars · BSD-3-Clause
B · leads
89.4
50,382 stars · AGPL-3.0
django-DefectDojo versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. django-DefectDojo is written mainly in Python; Metabase is written mainly in Clojure. The composite score is 85.7 for django-DefectDojo and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to django-DefectDojo's 5,244, a gap of 45,138 (9.61×). Forks are 2,026 for django-DefectDojo and 7,016 for Metabase. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 86 versus 100.
Push history: django-DefectDojo was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 301 for django-DefectDojo (0.057 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
django-DefectDojo is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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 96 for django-DefectDojo and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both django-DefectDojo (5,244 stars) and Metabase (50,382 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: django-DefectDojo is open source, Metabase is freemium.
The lead is split. django-DefectDojo is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on adoption (100 to 79). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against django-DefectDojo at 85.7, a 3.7 point narrow 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 | django-DefectDojo | Metabase |
|---|---|---|
| GitHub stars | 5,244 | 50,382 |
| Forks | 2,026 | 7,016 |
| Open issues | 301 | 4,696 |
| Adoption | 79 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 85.7 | 89.4 |
Open-Source Unified Vulnerability Management, DevSecOps & ASPM
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 5,244 for django-DefectDojo. The gap is 45,138 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both django-DefectDojo and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
django-DefectDojo is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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 django-DefectDojo scores 85.7. This page calls that a narrow lead for Metabase.