A
django-DefectDojo
87.1
5,244 stars · BSD-3-Clause
Analytics
langfuse leads by 1.5 · narrow
A
87.1
5,244 stars · BSD-3-Clause
B · leads
88.6
37,546 stars · license n/a
django-DefectDojo versus langfuse 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; langfuse is written mainly in TypeScript. The composite score is 87.1 for django-DefectDojo and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to django-DefectDojo's 5,244, a gap of 32,302 (7.16×). Forks are 2,026 for django-DefectDojo and 4,243 for langfuse. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 91 versus 100.
Push history: django-DefectDojo was last pushed on 17 November 2026 (0 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 301 for django-DefectDojo (0.057 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 52 and 70; 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. langfuse 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 96 for django-DefectDojo and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both django-DefectDojo (5,244 stars) and langfuse (37,546 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, langfuse is unpriced in this catalog.
The lead is split. django-DefectDojo is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on adoption (100 to 81). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against django-DefectDojo at 87.1, a 1.5 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 | langfuse |
|---|---|---|
| GitHub stars | 5,244 | 37,546 |
| Forks | 2,026 | 4,243 |
| Open issues | 301 | 1,173 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 87.1 | 88.6 |
Open-Source Unified Vulnerability Management, DevSecOps & ASPM
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
langfuse has more GitHub stars: 37,546 versus 5,244 for django-DefectDojo. The gap is 32,302 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both django-DefectDojo and langfuse 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. langfuse 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.
langfuse scores 88.6 and django-DefectDojo scores 87.1. This page calls that a narrow lead for langfuse.