deskreen

pavlobu/deskreen

Deskreen turns any device with a web browser into a secondary screen for your computer. ⭐️ Star to support our work!

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Jul 8, 2026
86 days ago
Ship score
31/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 21,337 → 21,525 (Aug 18 – Sep 29, 2026)
+142 stars in the 28 days to 2026-09-29

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
21.5K
Forks
1.2K
Open issues
18
Watchers
260
Primary language
TypeScript
Created
Aug 8, 2020
Owner
pavlobu · User

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

Topics

#blueprintjs#darkwire-io#deskreen#easy-to-use#electon-app#electron#electron-react-boilerplate#electronjs#end-to-end-encryption#linuxapp#macosapp#sceen-sharing-to-multiple-devices#second-screen#share-app-window#share-screen#testcafe#typescript#webrtc#wifi#windowsapp

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 80%, self-hostable 39%, hosted offering 22%. 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: slowed — last push 2026-07-08This is the badge for pavlobu/deskreen, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/pavlobu/deskreen.svg)](https://ossean.com/pavlobu/deskreen)

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.