checkbox's npm test script performs a live check-in
Check-in scripts for local use, cloud functions, or Qinglong, supporting over 40 Chinese sites and apps: Ciweimao Novels, Acfun, ShiguangXiangce, Shuxiangmendi forum, Shenshi Lingyu, Haoyoukuaibao, Maiduidui, Duokan Reading, Shanyi app, Xiangwang Novels, Jinjiang, Chenguang, Smzdm, NetEase Snail Reading, NetEase Cloud Gaming, Longkong forum, NGA forum, CSDN, MT forum, SF Light Novels, MaoerFM, Lenovo Zhixuan app, Shumazhijia, AIFengyue, Togamemod, Haoshuyou forum, YuC forum, FanRuan community, Cunhua forum, Documentary Home, Fugui forum, UG Fans, Yuciyuan forum, Cainiao Gallery, Meizu community, Jingguanzhijia, Youfenxiang forum, BigFun community, Qianmoju, HiFiNi, Hires Backyard, Ququyun Drive, Youxidongli, Baidu AiQiCha, Qingzhi Library, Qoo, Tianshi Dongman, Danman, LCSC, Jiepei, Huahuo forum, 17K, Chuzhan, Qidian Reading, Aolaxing Mall, Gongchuang, and McDonald's.
At a glance
- What is it?
- checkbox is a collection of daily check-in scripts for about ninety Chinese sites and apps, runnable under a Qinglong panel, under Termux on a cron schedule, or as a cloud function, with credentials supplied in a hand-edited YAML file. Its test script is a real sign-in against a live site, two Node built-ins are installed as packages, node_modules is committed, and the page forbids reposting while the metadata says MIT.
- Who is it for?
- checkbox suits someone who wants the daily points and coins from their own accounts collected on a schedule rather than by hand, and who is comfortable editing a YAML file with cookies in it. Before running it, read the licence question carefully, because the page carries a written ban on reposting while the package metadata says MIT, and those two statements conflict.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 7 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.
Star history
- Wenmoux/checkbox2,566 ★ · +1
| Repository | 2026-10-01 | 2026-11-13 |
|---|---|---|
| Wenmoux/checkbox | 2.6k | 2.6k |
1 Stars in the last 43 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The page forbids reposting and the metadata says MIT
Two statements about the licence sit in the same repository and they do not agree. The package metadata records the MIT licence and names an author, which on its own terms permits anyone to use, copy, modify, merge, publish, distribute, sublicense and sell the work, with the notice kept in copies. Above the check-in list, in coloured text and set as a heading of its own, the page says that reposting or carrying the work elsewhere without permission is forbidden. A reader who is MIT compliant and a reader who obeys the banner are being told different things, and the repository ships no separate licence file to settle it, only the `LICENSE` entry at the root. The page also explains the state of the code in one line: the author says that when the project started they did not know what JavaScript was and did not know programming, and that everything came from search engines and from copying other people's code.
The test script is a real sign-in against a live site
The script block in the package metadata has two entries and neither is a test suite:
"scripts": {
"test": "node index.js csdn",
"start": "node index.js"
}So running the project's test command executes the runner against one named target, CSDN, using whatever credentials the configuration file currently holds, over the network, against a site that will record the check-in. There is no assertion in it and no fixture, and the repository's entry list contains no test directory at all. A contributor who runs the obvious command to see whether the checkout works has therefore performed a live action on someone else's service. The same block also names the runner as `index.js`, while the prose tells you to execute `checkbox.js`, so the two entry points in the project do not agree on which file starts the work.
Two Node built-ins are installed as packages
The dependency list has eight entries and two of them should not be there. `crypto` is listed at a caret range, and `fs` is listed as version `0.0.1-security`, which is the placeholder version a certain class of squatted package name carries. Both modules are part of the runtime already, so installing them adds a download and a resolution step for nothing, and one of them adds a package whose only purpose is to exist. The rest of the list is a reasonable set for this kind of script: an HTTP client with its promise interface, a cryptography library, a character set conversion library for Chinese text, a YAML parser for the configuration file, a websocket client, and a command line argument parser. The interesting absence is a scheduler: the crontab side of the project is delegated to the host, whether that is a cron daemon under Termux or the panel's own scheduler.
The configuration file needs a space after every colon
The documented setup is four steps and one warning. Download the source, install the dependencies, copy the template configuration file to a new name, and then fill in the cookies for the sites you want. The warning is the interesting part: keep the existing format, and note that every colon must be followed by a space. That is a property of the format the template ships in, and it means a hand-edited line missing that single space changes how the file parses rather than producing an error message about the missing value. The file also carries the task list itself, under a key named for the callback list, which is what the panel instructions later tell you to edit. So the same file holds both the schedule of what runs and the credentials each task needs, and there is no separation between the two.
Three hosts, one task list and one opaque panel command
The same scripts are meant to run in three places, and each host has its own setup text. Locally, the project is documented against Termux on a phone, where the schedule is a crontab entry and the file that shows the syntax is shipped in the repository. As a panel, it is a Qinglong installation driven by a single repository command with five positional arguments: the repository URL, a pattern naming the install script, a branch selector, a list of directories to pull, and the branch to pull from. Then the prose adds manual steps in the panel's own settings file, telling you to add the shell extension to a configuration line, add a scheduled task in the interface, run the install task by hand, and fill the cookies into a configuration file under the panel's data directory. The panel route also carries a warning that it must be the latest version, or you create the configuration file yourself.
One task out of ninety documents a preview mode
Nearly ninety sites are on the list, and exactly one of them has a documented way to try it without acting. The Sector0x task takes an access token, a refresh token, an identity token and an expiry, plus a list of missions, a limit, a slot count and two output limits, and it comes with two switches whose meaning is stated: a preview flag that only shows what would happen, and a yes flag that has to be true for anything to actually be claimed or created. Everything else on the list is documented as a bare action, a daily check-in, a daily task set, or a lottery, with no equivalent switch named. The changelog follows the same shape, adding one site at a time with a date, and its most recent entry is a mission task from May 2026 while the repository's last commit is from June 2026.
Committed dependencies and two files named old
The root of the repository explains the heavy install step. Alongside the runner, the entry point, a template module, a notification module, a configuration template, the crontab example and two installer scripts there is a committed dependency directory, so the packages are versioned with the source rather than resolved on the machine. Two of the files carry an old suffix: a previous version of the runner and a previous version of the installer. Both are still there next to their replacements, which is what happens when a rewrite lands without deleting what it replaced. The tree also holds a changelog, a licence file and a readme, and nothing else: no test directory, no continuous integration file, and no issue templates. The project directs questions to a Telegram group and two QQ groups instead.
Editorial conclusion
checkbox suits someone who wants the daily points and coins from their own accounts collected on a schedule rather than by hand, and who is comfortable editing a YAML file with cookies in it. Before running it, read the licence question carefully, because the page carries a written ban on reposting while the package metadata says MIT, and those two statements conflict. Expect a script that talks to live third party sites on your behalf, so treat the cookie file as a credential and keep it out of version control. Notice that only one of the tasks documents a preview mode and an explicit confirmation flag, so for the rest the safe way to test a new task is to read its code rather than to run it.
Frequently asked questions
What does Wenmoux/checkbox do?
It is a collection of scripts that perform the daily check-in on about ninety Chinese sites and apps, collecting the points, coins or daily tasks each account earns. The same scripts are documented for three hosts: a phone under Termux with a crontab schedule, a Qinglong panel, and a cloud function. You supply your own cookies in a YAML configuration file.
How do I run checkbox?
Clone the repository, change into the directory, run `npm install`, then `node checkbox.js`. You can also name tasks on the command line, as in `node checkbox.js acfun csdn`, which is what the text recommends for scheduled runs. The package's own script block differs: its start script is `node index.js` and its test script is `node index.js csdn`.
How do I configure checkbox?
Copy `config.yml.temple` to `config.yml`, fill in the cookies for the sites you want and the list of tasks to run, and keep the existing format. The page warns that every colon in the file must be followed by a space, so a missing space changes how the file parses rather than reporting the missing value.
How do I run checkbox on a Qinglong panel?
With a single `ql repo` command carrying the repository URL, an install script pattern, a branch selector, the directories to pull and the branch name, then a scheduled task added in the panel, the install task run by hand, and cookies plus the task list filled into the panel's configuration file. The page warns that the panel must be the latest version or you create that file yourself.
Is checkbox safe to use?
The page makes no security claim. What it documents is that your cookies go into a YAML file, that one task additionally accepts access, refresh and identity tokens, that the dependency directory is committed to the repository, and that the project's own test script performs a live check-in against one named site.
Official sources
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.
[](https://hysenlabs.com/projects/wenmoux-checkbox)Star history chart for your README
[](https://hysenlabs.com/projects/wenmoux-checkbox)Was this useful?