What's inside Evil0ctal/Douyin_TikTok_Download_API

Evil0ctal/Douyin_TikTok_Download_API is a Python repo with 170,068 lines written. Douyin_TikTok_Download_API is built with net/http, FastAPI, uvicorn, and 2 more and uses Redis and Postgres. AI signed 0.2% of the 417 commits of Douyin_TikTok_Download_API.

Douyin_TikTok_Download_APIPython · Apache-2.0
lines written
170,068
files
348
test files
160
GitHub stars
21,177

Read on November 5, 2026, at commit 5aa0352.See each one with its proof

How much of Douyin_TikTok_Download_API did AI write?

0.2%

AI signed 0.2% of the 417 commits of Douyin_TikTok_Download_API.

Signed by an AIWithout one

Who writes it

Frequently asked questions

What is Evil0ctal/Douyin_TikTok_Download_API?
Evil0ctal/Douyin_TikTok_Download_API is a Python repo with 170,068 lines written. Its description on GitHub: “🚀 自托管的抖音、TikTok、B 站数据采集与无水印视频下载 API,支持 AI agent 通过 MCP 调用与离线语音转文字,Docker 一键部署。| Self-hosted TikTok, Douyin & Bilibili scraper and no-watermark video downloader — async REST API, MCP server for AI agents, CLI and web console, plus offline speech-to-text for downloaded videos. Self-healing identity pool, PostgreSQL archive, one docker compose up.”

The proof: its page on GitHub

What is Douyin_TikTok_Download_API built with?
Douyin_TikTok_Download_API is built with net/http, FastAPI, uvicorn, and 2 more and uses Redis and Postgres.

The proof: each service with its file and line

How much of Douyin_TikTok_Download_API did AI write?
AI signed 0.2% of the 417 commits of Douyin_TikTok_Download_API.

The proof: the commits each tool signed

What license does Douyin_TikTok_Download_API have?
Douyin_TikTok_Download_API is released under the Apache-2.0 license.

The proof: its page on GitHub

How many stars does Douyin_TikTok_Download_API have on GitHub?
Douyin_TikTok_Download_API had 21,177 stars on GitHub on November 5, 2026.

The proof: its page on GitHub

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →