hypit

hypit-ai/hypit

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 31, 2026
today
Ship score
91/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,542 → 25,882 (Sep 22 – Oct 27, 2026)
+8,627 stars in the 28 days to 2026-10-27

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
27.1K
Forks
3.1K
Open issues
77
Watchers
54
Primary language
TypeScript
License
Other
Created
Jul 29, 2026
Owner
hypit-ai · 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. 209 startups in the directory ship primarily in TypeScript.

Topics

#agentic-ai#ai#ai-agents#ai-video#compiler#dsl#ffmpeg#generative-ai#llm#markup-language#monorepo#plugin-system#programming-language#text-to-video#typescript#video#video-automation#video-clone#video-editing#video-generation

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 98%, self-hostable 33%, hosted offering 58%. 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.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.98. 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-31This is the badge for hypit-ai/hypit, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/hypit-ai/hypit.svg)](https://ossean.com/hypit-ai/hypit)

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.