Skip to content
DevUtils Online

Self-Hosted

linkwarden vs Stirling-PDF

Stirling-PDF leads by 8.1 · clear

linkwarden 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. Both projects are written mainly in TypeScript. The composite score is 83.1 for linkwarden and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to linkwarden's 20,462, a gap of 76,370 (4.73×). Forks are 894 for linkwarden and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 74 versus 100.

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

linkwarden 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. 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 52 for linkwarden and 30 for Stirling-PDF. This is a procurement signal, not legal advice.

In Self-Hosted, both linkwarden (20,462 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: linkwarden is open source, Stirling-PDF is unpriced in this catalog.

The lead is split. linkwarden is furthest ahead on license flexibility (52 to 30), while Stirling-PDF is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.

Stirling-PDF finishes ahead at 91.2 against linkwarden at 83.1, a 8.1 point clear 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.

linkwarden versus Stirling-PDF metrics
Signal linkwarden Stirling-PDF
GitHub stars 20,462 96,832
Forks 894 9,373
Open issues 705 448
Adoption 86 100
Activity 100 100
Community 74 100
Issue health 70 96
License 52 30
Self-hosting 100 100
Composite 83.1 91.2

linkwarden

⚡️⚡️⚡️ Self-hosted collaborative bookmark manager to collect, read, annotate, and fully preserve what matters, all in one place.

Project site · GitHub · Full profile

Questions this page answers

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

Stirling-PDF has more GitHub stars: 96,832 versus 20,462 for linkwarden. The gap is 76,370 stars.

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

Stirling-PDF was pushed more recently: 17 November 2026 versus 13 November 2026 for linkwarden. That is 3 days apart.

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

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

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

linkwarden 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. 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.

Who wins the linkwarden vs Stirling-PDF score?

Stirling-PDF scores 91.2 and linkwarden scores 83.1. This page calls that a clear lead for Stirling-PDF.

Related comparisons