Open-source project
qist/tvbox avatar
qist/tvbox

qist/tvbox ships twelve TVBox configs, most of them somebody else's jar

OK Video and TVBox configuration files. Fork for personal use if you like it. Please read the repo's instructions carefully before use; using it implies you understand them.

12,877 stars4,448 forksJavaScriptLicense varies

At a glance

What is it?
A configuration shelf for the OK影视, TVBox and 猫影视 app family: twelve JSON files, each pairing a jar and a source list contributed by a different person, plus four GitHub proxies and cloud drive token steps. There is no app here, no licence, and the README asks you to delete the repository within 24 hours.
Who is it for?
Adopt it if you want a frozen snapshot of a TVBox configuration for one television and accept that a person else's jar decides what plays. Do not adopt it for anything you ship: there is no LICENSE file among the top-level entries, no GitHub release to pin, and the disclaimer limits use to testing and study while barring commercial use.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • qist/tvbox12,877 ★ · +1,461
Star history
Repository2026-09-222026-11-13
qist/tvbox11.4k12.9k

1,461 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Twelve configs named after the day their jar was captured

It is mainly a shelf of configuration files for three apps in one family, described in the README as OK影视, TVBox and 猫影视 configurations, and JavaScript is recorded as the primary language, with js/, cat/, py/ and tools/ directories alongside the JSON files.

The filenames are dates. 0707.json is a multi-line interface config that works only on Fengmi影视. 0821.json is the large one, built on the 饭太硬 config with extra on-demand sources, live lines and parsers added. 0826.json traces back to 饭太硬 as well, 0825.json to Panda Groove's go jar, 0827.json to fongmi, 0828.json to 唐三, XBPQ.json to 小米小爆脾气, XYQ.json to 香雅情. js.json pairs Panda Groove's go jar with resources from 道长's drpy repository and adds YouTube live.

Read that list as a provenance record, not a feature list. Most entries are another person's jar plus another person's source list, republished under a date. The alternative to collecting them here is going straight to an upstream address such as 饭太硬's own, listed first among the external configs; the difference is that this repository freezes a snapshot under a dated name, while the upstream file changes under you. The maintainer's own contribution is the merge in jsm.json.

CatVodOpen changed its config URL at V1.1.3 and the two forms are not interchangeable

猫影视 pulls its configuration from a Git repository, and the instructions split on a version boundary. From V1.1.3 upward the address ends in an md5 file:

bash
github://[email protected]/xxxxx/tvbox/dist/index.js.md5

At V1.1.2 and below the same feature is addressed through Gitee and a different path:

bash
github://[email protected]/xxxxx/tvbox/js/open_config.json

What changed between them is given as a short changelog. quickjs was replaced with nodejs, proxy settings were modified, and on iOS local cannot be used, so db replaces every local method. nodejs is offered as the reason for the switch, being more flexible.

Two consequences follow from the shape of the address. A personal access token sits inline in the string rather than behind a prompt, so the address itself has to be treated as a secret wherever you copy it, paste it or screenshot it. And a config written for one side of the V1.1.3 boundary is not a config the other side reads, so a fork has to track the app version you actually run.

You fork to a private repository, because CatVodOpen refuses public ones

The import path is where most readers get stuck. A tutorial is linked at omii.top/1296.html, and one constraint is stated as a warning: import with Gitee or Github and set the repository to private, because CatVodOpen supports only private repositories and dav. In practice the first step is not installing anything. You fork the repository to an account you own, mark it private, and hand the app a github:// address carrying your own token.

The apps are separate projects, and seven are recommended with their differences spelled out. FongMi/TV is the OK影视 build, supporting multi-line live, automatic source switching, live speed and phone casting. q215613905/TVBoxOS supports live replay, and takagen99/Box supports live replay with a better looking interface. A 皮皮虾 build is distributed over Telegram and adds danmaku. catvod/CatVodOpen gives a plain interface across platforms, XiaoRanLiu3119/TVBoxOS-Mobile is a portrait phone build, and o0HalfLife0o/TVBoxOSC publishes compiled APKs of the q215613905 and takagen99 forks.

One setup line is easy to miss and expensive to ignore. The app must be given storage permission, otherwise authentication is lost and it cannot write to disk.

0825.json is unusable until you substitute your own proxy url

One of the twelve configs ships unfinished. 0825.json is the small and precise one, with its jar taken from Panda Groove's go package, and the note is that sources such as 泥巴 and 星星 need your own proxy url substituted before the file works. That is the difference between this repository and a product you can install: one file out of twelve is a template, and nothing tells you which field to edit or what a valid value looks like.

jsm.json is the opposite case, and it is the maintainer's own merge of js.json and 0826.json. YouTube live is removed because the merged file targets a family television, it is marked usable in OK影视, televisions are advised to use OK影视, and multi-live selection is kept. The same file also appears as the maintainer's personal television entry with a direct raw address. js.json is what you pick if YouTube live matters to you, and jsm.json is what you pick if it does not.

Sorted by name, these two look interchangeable. They are not, and nothing in the filenames tells you which one has content behind it.

Four GitHub proxies and a Cloudflare Pages mirror, with no policy behind any of them

Because raw.githubusercontent.com is often slow or blocked on the networks these apps run on, four GitHub proxies are offered with the instruction to pick whichever is fast:

bash
https://github.moeyy.xyz https://mirror.ghproxy.com/ https://gh-proxy.com https://ghproxy.net

The same file is reachable through a Cloudflare Pages build:

bash
https://qist.wyfc.qzz.io/jsm.json

Two more interfaces come in pairs, the 潇洒 api at xiaosa/api.json and the 饭太硬 interface at fty.json, each offered as both a raw.githubusercontent address and a qist.wyfc.qzz.io counterpart. Twelve external configuration addresses are listed, running from 饭太硬 through okjack, 王二小放牛娃, 摸鱼儿, Ray, 俊于 and others.

The trade is availability for trust. Every one of those hosts sees your requests, and the README gives no operator, no retention policy and no fallback order. Speed is the only selection criterion it states, which is not enough to decide where a request stream should go.

Aliyun Drive above 10 connections and Xunlei single-token use can close your account

The cloud drive section is the part with consequences outside the repository. Configuration happens under 配置 | 中心. Two warnings come first, and both are about the account you sign in with rather than about the config. Aliyun Drive is said to require that users not use multi-threaded acceleration, and concurrent connections above 10 may lead to restricted access or a banned account, with the risk of any setting above 10 left for the reader to weigh. Xunlei Drive is described as extremely strict: no single token across multiple users or locations, and no multi-threaded use, because an account may be closed at any time.

The shortcuts work the same way. Scanning any OpenToken in the 网盘及弹幕配置 source automatically activates 转存原画, and that source is the fast route to a 32-bit token and an opentoken. Two repair notes follow. If 极速GO原画 errors repeatedly and quickly, that may not be a ban, so kill the player and restart, or restart the device. If 转存原画 is capped near 2M, log out of the Aliyun Drive app, log back in, then delete the TV folder from the device's SD card.

That last instruction is the honest summary. The state that makes playback work is not durable, and the repair touches your cloud login and your SD card.

No LICENSE file, no releases, and a disclaimer that asks you to delete the repository in 24 hours

No licence file sits among the top-level entries and the licence is recorded as unknown, so nothing is granted. The default branch is master, the repository is not archived, and the last push was on 2026-11-02. There are no GitHub releases, so nothing is versioned by tag either, and a config URL pinned to master can change contents under you.

The disclaimer is unusually direct. All resources come from free sharing by various contributors, and the manager cannot guarantee the legality, accuracy, completeness or validity of the content. Use is limited to testing and study, commercial use is prohibited, republication by public accounts or self-media is forbidden, and use inside the People's Republic of China is discouraged at your own risk. Third-party hardware and software carry no relation to the repository. Anyone who reads or uses the content, directly or indirectly, is to finish studying within 24 hours and delete it, and anyone who wants the functionality is told to develop it themselves. The closing line says updates happen as far as the maintainer can manage, with no guarantee of validity or timeliness.

For a company the answer is short. No licence, no warranty, no tag, and content pointing at other people's jars. Fork it for one living room television if that is the whole job. Do not put jsm.json in front of users as your own product, and do not build a release process on a master branch that the README describes as best-effort.

Editorial conclusion

Adopt it if you want a frozen snapshot of a TVBox configuration for one television and accept that a person else's jar decides what plays. Do not adopt it for anything you ship: there is no LICENSE file among the top-level entries, no GitHub release to pin, and the disclaimer limits use to testing and study while barring commercial use. Verify first that the filename you picked still exists in the tree, because four of the twelve documented names are not there, and check that the app you run sits on the same side of the CatVodOpen V1.1.3 boundary as the github:// address you are about to paste.

Frequently asked questions

What is qist/tvbox and what am I supposed to do with the JSON files?

It is a collection of configuration files for the OK影视, TVBox and 猫影视 apps rather than an app itself. Twelve JSON configs are documented, each pairing a jar from another project with a source list, and the repository asks you to fork it for your own use.

Why does qist/tvbox ask me to make my fork a private repository?

Because CatVodOpen supports only private repositories and dav, so the import must go through Gitee or Github with the repository set to private. The config address also embeds your personal access token inline rather than prompting for it.

Can I use the qist/tvbox configs commercially?

No. The disclaimer limits use to testing and learning research, prohibits commercial use, and forbids republication by public accounts or self-media. No LICENSE file appears among the repository's top-level entries, so no rights are granted beyond that.

Which qist/tvbox config should a family television use?

jsm.json is the one described as usable on a family television, with YouTube live removed and multi-live selection kept, and it doubles as the maintainer's personal television entry. js.json is the variant that keeps YouTube live.

What happens if I set more than 10 Aliyun Drive threads with qist/tvbox?

The README warns that Aliyun Drive may restrict access or ban an account when concurrent connections exceed 10, and that the risk of going above 10 is for the reader to weigh. Xunlei Drive is described as stricter still, with bans possible at any time.

Official sources

  1. Issues
  2. qist/tvbox on GitHub
  3. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/qist-tvbox.svg)](https://hysenlabs.com/projects/qist-tvbox)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/qist-tvbox.svg)](https://hysenlabs.com/projects/qist-tvbox)

Was this useful?