VideoLingo

Huanshere/VideoLingo

Netflix-level subtitle cutting, translation, alignment, and even dubbing - one-click fully automated AI video subtitle team | Netflix级字幕切割、翻译、对齐、甚至加上配音,一键全自动视频搬运AI字幕组

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Sep 30, 2026
22 days ago
Ship score
64/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 18,387 → 18,848 (Sep 8 – Oct 20, 2026)
+351 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
18.9K
Forks
2.1K
Open issues
23
Watchers
109
Primary language
Python
Created
Aug 9, 2024
Owner
Huanshere · 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. 111 startups in the directory ship primarily in Python.

Topics

#ai-translation#dubbing#localization#video-translation#voice-cloning

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 47% (self-hostable 62%, hosted offering 27%). 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. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

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-09-30This is the badge for Huanshere/VideoLingo, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/Huanshere/VideoLingo.svg)](https://ossean.com/Huanshere/VideoLingo)

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.