qist/tvbox: A Personal TVBox Configuration Repository Explained

What qist/tvbox actually is, and who it is for

This is not an application. It is a set of configuration files that a TVBox-family player reads at startup: eleven numbered or named JSON files at the repository root, plus directories such as FTY/, XBPQ/, XYQ/, cat/, js/, jar/, live/ and tools/. The README describes each JSON file by its origin rather than its contents. 0707.json is described as an OK影视 multi-line configuration interface that only works with Fengmi影视. 0821.json is described as a large, all-inclusive configuration built on top of the 饭太硬 configuration with additional on-demand sources, live channels and parsers. 0822.json is the minimal one, using OK's jar plus a few 路飞 and 俊于 sources. 0825.json is small and focused, with the jar coming from Panda Groove's Go package, and the README notes that sources such as 泥巴 and 星星 need to be replaced with your own proxy URL. The remaining files (0826.json, 0827.json, 0828.json, js.json, XBPQ.json, XYQ.json, cat.json, jsm.json) follow the same pattern of naming the upstream author or project.

The audience is narrow and stated plainly: the repository is described as a personal repository, and the instruction is to fork it for your own use. If you are looking for a maintained distribution with a changelog, this is the wrong shape of project. The last push was on 2026-09-21, so the repository is current, but there are no releases, no tags and no documentation of what changed between files.

How a TVBox client consumes these JSON files

The mechanism is a URL. A TVBox client stores a configuration address and fetches that JSON over HTTP when it starts or when the user refreshes it. The JSON describes where the player should look for content: which jar or Go binary handles parsing, which site entries exist, and which live stream lists to load. The README shows this shape for 猫影视, which accepts a github:// or gitee:// URL with an embedded token.

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

The README states this form applies to CatVodOpen V1.1.3 and above, and that the client only supports private repositories and dav. For V1.1.2 and below the documented form is a different path:

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

Two changes are listed for the newer version: quickjs was replaced by nodejs, and the proxy setting was modified. The README also notes that local storage does not work on iOS, so db replaces all local methods there. That is the whole architecture as documented: static JSON plus a parser binary, resolved at client startup, with no server component in this repository. The live/ and list.m3u, list.txt, listx.m3u, listx.txt, radio.m3u, radio.txt files are the live channel side of the same idea, and jsm.json is described as a merge of js.json and 0826.json with the YouTube live entry removed for home television use.

Installing and loading a configuration for the first time

There is nothing to install from this repository. The install step belongs to the client. The README recommends several apps and gives their project addresses: OK影视 at github.com/FongMi/TV, the q215613905 build at github.com/q215613905/TVBoxOS, the takagen99 build at github.com/takagen99/Box, the 皮皮虾 build via a Telegram channel, the new 猫影视 at github.com/catvod/CatVodOpen, a phone-oriented build at github.com/XiaoRanLiu3119/TVBoxOS-Mobile, and a compile repository at github.com/o0HalfLife0o/TVBoxOSC. Install one of those first.

Then fork this repository, because the README asks you to. The raw URL pattern the README uses for its own files is the standard raw.githubusercontent.com path, for example the self-use television configuration:

https://raw.githubusercontent.com/qist/tvbox/master/jsm.json

For networks where raw.githubusercontent.com is slow, the README lists proxy prefixes and says to pick a fast one:

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

The README also documents a Cloudflare Pages deployment of the same content at https://qist.wyfc.qzz.io/jsm.json, and two additional endpoints: https://raw.githubusercontent.com/qist/tvbox/master/xiaosa/api.json and https://raw.githubusercontent.com/qist/tvbox/master/fty.json. Paste the chosen URL into the client's configuration field and refresh. One warning in the README is easy to miss and causes confusing failures: the app must be granted storage permission, otherwise authentication is lost because the client cannot write to disk.

Cloud drive authorization and the concurrency limits the README warns about

A large part of the practical value here is the cloud drive side, configured through the 《 配置 | 中心 》 menu. The README carries two explicit warnings. The first concerns Alibaba Cloud Drive: it says users are reportedly not allowed to use multi-threaded acceleration, and that exceeding 10 concurrent connections may lead to access restriction or account bans, with the risk left to the user if the thread limit is set above 10. The second concerns Xunlei Cloud Drive, described as extremely strict, with a warning against using a single token across multiple users in different locations or with multiple threads.

The README also describes a convenience path: the 网盘及弹幕配置 video source can be used to obtain a 32-digit token and opentoken, and scanning any OpenToken in that menu automatically activates the 转存原画 feature. Two troubleshooting notes are given. If 极速GO 原画 repeatedly errors, the README says it is not necessarily a ban and suggests killing the player or restarting the playback device. If 转存原画 speed is capped around 2M, it suggests logging out of the Alibaba Cloud Drive app, logging back in, and deleting the TV directory on the playback device's SD card. These are user-reported remedies, not documented guarantees, and the README does not explain why they work.

Where qist/tvbox breaks down

The README is candid about the main failure mode: it says it updates as far as it can and does not guarantee the validity or timeliness of the configurations. That is not boilerplate. These JSON files point at third-party sources, jars and stream endpoints that change or disappear without notice, and nothing in the repository pins or verifies them. A configuration that loaded last month can fail today with no change on your side.

Several entries need work before they are usable at all. 0825.json is documented as requiring you to replace sources such as 泥巴 and 星星 with your own proxy URL. js.json depends on a Go package from Panda Groove and resources from the 道长 drpy repository. If you are not prepared to edit JSON and host the result yourself, most of these files are not drop-in. The repository also has no releases, so there is no versioned artifact to pin to and no way to roll back to a known-good configuration other than keeping your own copy. The licence is not stated in the repository, which means the terms under which you may redistribute or reuse the contents are simply not documented here; the README instead forbids commercial use, forbids reposting by 公众号 and 自媒体, and states the content is for testing and study only and should be deleted within 24 hours. Whether that is enforceable is a separate question, but it tells you the author does not intend this as a redistributable package.

Alternatives: upstream configurations and other client builds

The most direct alternative is to skip this repository and use one of the upstream configurations the README itself lists. 饭太硬 at http://www.饭太硬.top/tv/ is the base for 0821.json and the entire source for 0826.json. okjack at https://jihulab.com/okcaptain/kko/raw/main/ok.txt, 霜辉月明py at the PyramidStore repository, 南风 at the agit.ai mirror, and 俊于 at http://home.jundie.top:81/top98.json are all listed as separate configurations. The difference in approach is maintenance ownership: going upstream means you follow that author's changes directly, while qist/tvbox means you follow whatever this author chose to merge, and the README gives no merge policy or update cadence beyond the general statement that it updates as far as it can.

The other axis is the client. The README lists seven apps with different feature sets: OK影视 supports multiple live lines, automatic source switching, live playback speed and phone screen casting; q215613905 and takagen99 support live replay; 皮皮虾 adds danmaku; CatVodOpen is described as having a simple interface and multi-platform support; TVBoxOS-Mobile is portrait-oriented. Choosing a client changes what parts of these JSON files are even meaningful, since 0707.json is explicitly limited to Fengmi影视.

Maintenance, licence and the cost of keeping it working

The last push was on 2026-09-21 and the repository is not archived, so the content is being touched. There are no releases, which means upgrades are a git pull or a re-fork, and the practical cost is not the pull but the re-verification: after any update you need to confirm that the specific JSON file you load still resolves and that its sources still respond. Because the README disclaims validity and timeliness, that verification is your responsibility by the author's own statement.

The licence field is unknown, and the README does not fill the gap. What it does say is a set of restrictions: content is for testing and study only, commercial use is prohibited, reposting by 公众号 or 自媒体 in any form is prohibited, and use inside mainland China is explicitly disclaimed with consequences left to the user. It also states that all resources come from other people's sharing and that infringement complaints will be honored with removal. Treat that as a description of the author's intent, not as a licence grant, and note that the repository contains third-party jar packages and Go binaries whose own terms are not documented here either.

Editorial conclusion

Adopt qist/tvbox only if you already run a compatible client such as OK影视, TVBoxOS or CatVodOpen and you are willing to fork the repository and host the JSON yourself. Do not adopt it if you need a maintained product, a support channel, or any statement about legality: the README disclaims accuracy, completeness and validity, and the licence is not stated anywhere in the repository. Before anything else, verify that the specific JSON file you intend to load still resolves, because the README itself says it does not guarantee the validity or timeliness of the configurations.

Frequently asked questions

Official sources

1. Issues
2. qist/tvbox on GitHub
3. README