Skip to content
DevUtils Online

Self-Hosted

Stirling-PDF vs TREK

Stirling-PDF leads by 5.7 · narrow

B

TREK

85.5

15,696 stars · AGPL-3.0

Stirling-PDF versus TREK is a Self-Hosted 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 Stirling-PDF and 85.5 for TREK.

Stirling-PDF has 96,832 GitHub stars to TREK's 15,696, a gap of 81,136 (6.17×). Forks are 9,373 for Stirling-PDF and 1,342 for TREK. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 79.

Push history: Stirling-PDF was last pushed on 17 November 2026 (0 days ago), and TREK was last pushed on 17 November 2026 (0 days ago). Open issues stand at 448 for Stirling-PDF (0.005 per star) and 19 for TREK (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.

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. TREK 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. License scores in this pair are 30 for Stirling-PDF and 52 for TREK. This is a procurement signal, not legal advice.

In Self-Hosted, both Stirling-PDF (96,832 stars) and TREK (15,696 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: Stirling-PDF is unpriced in this catalog, TREK is open source.

The lead is split. Stirling-PDF is furthest ahead on fork community (100 to 79), while TREK is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.

Stirling-PDF finishes ahead at 91.2 against TREK at 85.5, a 5.7 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Stirling-PDF versus TREK metrics
Signal Stirling-PDF TREK
GitHub stars 96,832 15,696
Forks 9,373 1,342
Open issues 448 19
Adoption 100 84
Activity 100 100
Community 100 79
Issue health 96 96
License 30 52
Self-hosting 100 100
Composite 91.2 85.5

TREK

The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Stirling-PDF or TREK?

Stirling-PDF has more GitHub stars: 96,832 versus 15,696 for TREK. The gap is 81,136 stars.

Which was updated more recently, Stirling-PDF or TREK?

Both were last pushed on 17 November 2026.

Can I self-host both Stirling-PDF and TREK?

Yes. This catalog marks both Stirling-PDF and TREK as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Stirling-PDF or TREK?

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. TREK 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Stirling-PDF vs TREK score?

Stirling-PDF scores 91.2 and TREK scores 85.5. This page calls that a narrow lead for Stirling-PDF.

Related comparisons