A
bore
75.1
11,615 stars · MIT
Self-Hosted
unsloth leads by 22.8 · decisive
A
75.1
11,615 stars · MIT
B · leads
97.9
79,671 stars · Apache-2.0
bore versus unsloth is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bore is written mainly in Rust; unsloth is written mainly in Python. The composite score is 75.1 for bore and 97.9 for unsloth.
unsloth has 79,671 GitHub stars to bore's 11,615, a gap of 68,056 (6.86×). Forks are 531 for bore and 7,439 for unsloth. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 70 versus 100.
Push history: bore was last pushed on 04 February 2026 (286 days ago), and unsloth was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for bore (0.002 per star) and 469 for unsloth (0.006 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.
bore 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. unsloth 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 96 for bore and 96 for unsloth. This is a procurement signal, not legal advice.
In Self-Hosted, both bore (11,615 stars) and unsloth (79,671 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: bore is open source, unsloth is open source.
The lead is split. bore is furthest ahead on issue health (96 to 84), while unsloth is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
unsloth finishes ahead at 97.9 against bore at 75.1, a 22.8 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 | bore | unsloth |
|---|---|---|
| GitHub stars | 11,615 | 79,671 |
| Forks | 531 | 7,439 |
| Open issues | 19 | 469 |
| Adoption | 83 | 100 |
| Activity | 36 | 100 |
| Community | 70 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 75.1 | 97.9 |
🕳 bore is a simple CLI tool for making tunnels to localhost
Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.
unsloth has more GitHub stars: 79,671 versus 11,615 for bore. The gap is 68,056 stars.
unsloth was pushed more recently: 17 November 2026 versus 04 February 2026 for bore. That is 286 days apart.
Yes. This catalog marks both bore and unsloth as self-hostable. Confirm each project's deploy docs before you plan a migration.
bore 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. unsloth 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.
unsloth scores 97.9 and bore scores 75.1. This page calls that a decisive lead for unsloth.