A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 6.9 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
87.8
17,335 stars · MIT
dbeaver versus libsql is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbeaver is written mainly in Java; libsql is written mainly in C. The composite score is 94.7 for dbeaver and 87.8 for libsql.
dbeaver has 52,455 GitHub stars to libsql's 17,335, a gap of 35,120 (3.03×). Forks are 4,460 for dbeaver and 564 for libsql. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 75.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and libsql was last pushed on 07 November 2026 (10 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 490 for libsql (0.028 per star). Issue-health scores are 52 and 70; activity scores are 100 and 92.
dbeaver 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. libsql is listed as MIT, 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 96 for dbeaver and 96 for libsql. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and libsql (17,335 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: dbeaver is open source, libsql is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 75), while libsql is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against libsql at 87.8, a 6.9 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 | dbeaver | libsql |
|---|---|---|
| GitHub stars | 52,455 | 17,335 |
| Forks | 4,460 | 564 |
| Open issues | 3,349 | 490 |
| Adoption | 100 | 90 |
| Activity | 100 | 92 |
| Community | 100 | 75 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 87.8 |
Free universal database tool and SQL client
libSQL is a fork of SQLite that is both Open Source, and Open Contributions.
dbeaver has more GitHub stars: 52,455 versus 17,335 for libsql. The gap is 35,120 stars.
dbeaver was pushed more recently: 17 November 2026 versus 07 November 2026 for libsql. That is 10 days apart.
Yes. This catalog marks both dbeaver and libsql as self-hostable. Confirm each project's deploy docs before you plan a migration.
dbeaver 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. libsql is listed as MIT, 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.
dbeaver scores 94.7 and libsql scores 87.8. This page calls that a narrow lead for dbeaver.