A
bore
74.4
11,615 stars · MIT
Self-Hosted
Stirling-PDF leads by 16.8 · decisive
A
74.4
11,615 stars · MIT
B · leads
91.2
96,832 stars · license n/a
bore versus Stirling-PDF 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; Stirling-PDF is written mainly in TypeScript. The composite score is 74.4 for bore and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to bore's 11,615, a gap of 85,217 (8.34×). Forks are 531 for bore and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 69 versus 100.
Push history: bore was last pushed on 04 February 2026 (286 days ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for bore (0.002 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 96 and 96; 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. Stirling-PDF 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 bore and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both bore (11,615 stars) and Stirling-PDF (96,832 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, Stirling-PDF is unpriced in this catalog.
The lead is split. bore is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
Stirling-PDF finishes ahead at 91.2 against bore at 74.4, a 16.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 | Stirling-PDF |
|---|---|---|
| GitHub stars | 11,615 | 96,832 |
| Forks | 531 | 9,373 |
| Open issues | 19 | 448 |
| Adoption | 82 | 100 |
| Activity | 36 | 100 |
| Community | 69 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 74.4 | 91.2 |
🕳 bore is a simple CLI tool for making tunnels to localhost
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 11,615 for bore. The gap is 85,217 stars.
Stirling-PDF 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 Stirling-PDF 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. Stirling-PDF 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.
Stirling-PDF scores 91.2 and bore scores 74.4. This page calls that a decisive lead for Stirling-PDF.