Skip to content
DevUtils Online

Self-Hosted

neko vs Stirling-PDF

Too close to call · 91.0 to 91.2

A · level

neko

91.0

22,688 stars · Apache-2.0

neko 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. neko is written mainly in Go; Stirling-PDF is written mainly in TypeScript. The composite score is 91.0 for neko and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to neko's 22,688, a gap of 74,144 (4.27×). Forks are 1,662 for neko and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 81 versus 100.

Push history: neko was last pushed on 16 November 2026 (1 day ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 144 for neko (0.006 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

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

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

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

Composite score: neko 91.0, Stirling-PDF 91.2. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.

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.

neko versus Stirling-PDF metrics
Signal neko Stirling-PDF
GitHub stars 22,688 96,832
Forks 1,662 9,373
Open issues 144 448
Adoption 87 100
Activity 100 100
Community 81 100
Issue health 84 96
License 96 30
Self-hosting 100 100
Composite 91.0 91.2

Questions this page answers

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

Stirling-PDF has more GitHub stars: 96,832 versus 22,688 for neko. The gap is 74,144 stars.

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

Stirling-PDF was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.

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

Yes. This catalog marks both neko 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, neko or Stirling-PDF?

neko 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. 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 neko vs Stirling-PDF score?

Neither tool clears a one-point margin. neko scores 91.0 and Stirling-PDF scores 91.2.

Related comparisons