chathub

chathub-dev/chathub

This repository is in the OSSEAN directory, but it has no description on GitHub.

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Feb 27, 2026
217 days ago
Ship score
10/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 10,647 → 10,656 (Aug 18 – Sep 29, 2026)
+7 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
10.7K
Forks
1.1K
Open issues
15
Watchers
72
Primary language
TypeScript
Created
Mar 4, 2023
Owner
chathub-dev · Organization

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

#all-in-one#browser-extension#chrome-extension#react#typescript

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 90%, self-hostable 20%, hosted offering 52%. 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: silent — last push 2026-02-27This is the badge for chathub-dev/chathub, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/chathub-dev/chathub.svg)](https://ossean.com/chathub-dev/chathub)

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.