jitsi-meet

jitsi/jitsi-meet

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 9, 2026
today
Ship score
99/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 29,806 → 30,044 (Aug 25 – Oct 6, 2026)
+158 stars in the 28 days to 2026-10-06

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
30.1K
Forks
8.1K
Open issues
138
Watchers
522
Primary language
TypeScript
Created
Dec 16, 2013
Owner
jitsi · 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. 213 startups in the directory ship primarily in TypeScript.

Topics

#debian#deep-video#jitsi#jitsi-meet#scalable-video-conferences#sfu#video#video-communication#video-conferencing#webrtc

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 86%, self-hostable 76%, hosted offering 85%. 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-09This is the badge for jitsi/jitsi-meet, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/jitsi/jitsi-meet.svg)](https://ossean.com/jitsi/jitsi-meet)

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.