A · leads
Grafana
91.2
77,962 stars · AGPL-3.0
DevOps
Grafana leads by 21.5 · decisive
A · leads
91.2
77,962 stars · AGPL-3.0
B
69.7
5,333 stars · Apache-2.0
Grafana versus ThreatMapper is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 91.2 for Grafana and 69.7 for ThreatMapper.
Grafana has 77,962 GitHub stars to ThreatMapper's 5,333, a gap of 72,629 (14.62×). Forks are 14,988 for Grafana and 631 for ThreatMapper. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 67.
Push history: Grafana was last pushed on 17 November 2026 (0 days ago), and ThreatMapper was last pushed on 01 June 2026 (169 days ago). Open issues stand at 3,310 for Grafana (0.042 per star) and 144 for ThreatMapper (0.027 per star). Issue-health scores are 70 and 70; activity scores are 100 and 36.
Grafana 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. ThreatMapper is listed as Apache-2.0, 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. License scores in this pair are 52 for Grafana and 96 for ThreatMapper. This is a procurement signal, not legal advice.
In DevOps, both Grafana (77,962 stars) and ThreatMapper (5,333 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: Grafana is freemium, ThreatMapper is open source.
The lead is split. Grafana is furthest ahead on recent activity (100 to 36), while ThreatMapper is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Grafana finishes ahead at 91.2 against ThreatMapper at 69.7, a 21.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 | Grafana | ThreatMapper |
|---|---|---|
| GitHub stars | 77,962 | 5,333 |
| Forks | 14,988 | 631 |
| Open issues | 3,310 | 144 |
| Adoption | 100 | 76 |
| Activity | 100 | 36 |
| Community | 100 | 67 |
| Issue health | 70 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 69.7 |
Grafana is the dashboard and visualization layer most teams pair with Prometheus and other metric stores. The open-source server can be self-hosted; Grafana Labs sells a cloud.
Open Source Cloud Native Application Protection Platform (CNAPP)
Grafana has more GitHub stars: 77,962 versus 5,333 for ThreatMapper. The gap is 72,629 stars.
Grafana was pushed more recently: 17 November 2026 versus 01 June 2026 for ThreatMapper. That is 169 days apart.
Yes. This catalog marks both Grafana and ThreatMapper as self-hostable. Confirm each project's deploy docs before you plan a migration.
Grafana 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. ThreatMapper is listed as Apache-2.0, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Grafana scores 91.2 and ThreatMapper scores 69.7. This page calls that a decisive lead for Grafana.