Stirling-PDF

Stirling-Tools/Stirling-PDF

#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 22, 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 91,470 → 94,557 (Sep 8 – Oct 20, 2026)
+1,762 stars in the 28 days to 2026-10-20

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
94.7K
Forks
11.4K
Open issues
551
Watchers
296
Primary language
TypeScript
License
Other
Created
Jan 27, 2023
Owner
Stirling-Tools · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 210 startups in the directory ship primarily in TypeScript.

Topics

#docker#hacktoberfest#java#pdf#pdf-converter#pdf-editor#pdf-manipulation#pdf-merger#pdf-ocr#pdf-tools#pdf-web-apps#pdfmerger#self-hosted

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 99%, self-hostable 76%, hosted offering 57%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-22This is the badge for Stirling-Tools/Stirling-PDF, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/Stirling-Tools/Stirling-PDF.svg)](https://ossean.com/Stirling-Tools/Stirling-PDF)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.