Jsnzkpg: a daily-refreshed free node subscription repository on GitHub

What Jsnzkpg actually publishes, and who it is for

The repository's README does not describe a program. It is an index: a table of links to a Telegram channel, a Telegram group, a permanent node subscription, a permanent IPTV subscription, a TVbox subscription, and an aggregation site at jsnzkpg.com. The project description says it has been maintained for over five years, that availability is checked every day, and that it filters free nodes aggressively enough to call the result high quality. Those claims come from the description, not from a script you can read in the repository, because the top level of the default branch holds only Jsnzkpg and README.md.

So the audience is narrow and specific. You are the target user if you already run a proxy client that accepts a subscription URL: the description names shadowrocket, stash, singbox, clash, karing, hiddify, mihomo, clashmi, ClashMeta, FIClash and Surfboard. You paste a URL, the client pulls a node list, and you connect. You are not the target user if you want to run the collection pipeline yourself, audit how nodes are selected, or read a changelog of what was removed and why. None of that is in the README.

The subscription URL is the product; the repository is the storefront

The mechanism visible in the README is a subscription link. The row labelled permanent node subscription points at sub.445569.xyz, and the README gives it as a copyable address rather than a file in the repository. In client terms, that means the node list is served from that host, and the GitHub repository acts as the page that tells you the address exists.

The README also lists a permanent IPTV subscription at iptv.445569.xyz/live.m3u and a TVbox subscription routed through gh-proxy.org to a raw.githubusercontent.com path under the Jsnzkpg repository. Those two are separate products bundled on the same page, which is worth noticing: the repository is a distribution point for several link types, not a single-purpose node feed.

What the README does not show is the update path. There is no workflow file, no script, no cron entry and no data file in the top-level listing, so a reader cannot confirm from the repository how the daily availability check is implemented or what threshold a node must pass to stay in the list. The description asserts the filtering happens. The repository does not show it. Treat the quality claim as a claim.

Pasting the Jsnzkpg subscription into a client

There is no install step, because there is nothing to install from this repository. The README tells you to copy the subscription address, so the first real use is pasting it into a client you already have. The README publishes these two addresses for copying:

# node subscription:  https://sub.445569.xyz
# IPTV subscription:  https://iptv.445569.xyz/live.m3u

The node subscription is the one a proxy client consumes. In Shadowrocket, sing-box, Karing, Hiddify, mihomo, ClashMeta, FIClash or Surfboard the subscription is added through the client's own subscription screen, and you paste the address there. The README does not give a configuration file, a command or a flag for any of these clients, so the client's own interface is the only documented path. After the client fetches the list, you should see a set of nodes appear and be able to select one and connect. If the list comes back empty or the client reports a parse error, the subscription did not return a node list in the format that client expects, which is a normal failure mode for a shared free subscription.

The IPTV address is a plain M3U link that any IPTV player can open, and it is unrelated to the proxy nodes. The README's TVbox link is wrapped in gh-proxy.org, which suggests the raw GitHub path is reached through a third-party mirror rather than directly. If you use that link, you depend on that mirror.

Where Jsnzkpg breaks down: shared nodes, no rollback, no licence

A free subscription shared publicly has a predictable failure mode. The more people use the same node list, the more load each node carries, and the faster nodes are blocked or rate-limited. The README's claim of daily availability checks is a mitigation for dead nodes, not for congestion, and the repository does not document how a node is scored or how often the list changes size.

There is also no rollback story. If an update removes nodes that worked for you, the README does not document a way to pin an older list, and the repository's top level holds no versioned data files to fall back to. The recent release entry for this repository is named Jsnzkpg (TG频道@stymei1) and dated 2025-08-07, which is a release label rather than a downloadable artifact with notes. Anyone who needs a stable endpoint with a documented change history is looking at the wrong tool.

Licensing is another gap. The repository does not state a licence. Without a stated licence, the terms under which the subscription content or any bundled file may be reused are unclear, and that is a question for the project's own channel rather than something a reader should assume. Finally, the repository is maintained by an individual or small group publishing under a Telegram identity, so the support channel is a chat, not an issue tracker with commitments. If you need someone accountable for an outage, this is not that.

Jsnzkpg versus running your own collector

The obvious alternative is a self-hosted node collector: a scheduled job that pulls candidate nodes from public sources, tests them, and writes your own subscription file. The difference in approach is ownership. With Jsnzkpg you consume someone else's filtered list and inherit their selection criteria, their update cadence and their outages. With your own collector you control the test method, the retention rules and the output format, and you can version the result.

The cost is the reverse of the benefit. A collector needs a host that runs on a schedule, a test target, and enough maintenance that it keeps working when upstream sources change shape. Jsnzkpg exists precisely because most users do not want that job. If you want a URL to paste and nothing else, the repository is the shorter path. If you want to know why a node was dropped, no public subscription can answer that, and a collector you wrote can.

A second alternative is a paid subscription service, which the README itself advertises in its first table row. That trades the unpredictability of free shared nodes for a bill and, usually, a stated service level. The README does not compare the two beyond placing the advertisement at the top, so the choice is yours to make on cost and reliability rather than on anything documented here.

Maintenance, upgrade cost and licence status

The repository is not archived, and the last push was on 2026-09-19. That is consistent with the description's claim of daily availability checks, and it is the only maintenance signal available: there is no issue history, no changelog and no workflow file in the visible repository to corroborate the cadence.

Upgrade cost is close to zero for the consumer. Because the subscription is fetched by the client, you do not pull, build or redeploy anything; you update the URL in your client, or the client refreshes it on whatever interval it uses. The maintenance burden sits on the project side, and the visible sign of it is the last push date. If that date stops moving, the subscription should be treated as stale regardless of what the description says.

The licence is not stated in the repository. That matters if you plan to redistribute the list, bundle it into another product, or mirror the subscription. Without a stated licence you have no documented permission to do any of that, and the safe reading is that the subscription is for personal client use. This is not legal advice; it is a note that the repository is silent on the question.

Editorial conclusion

Jsnzkpg suits people who already run Clash, Shadowrocket, sing-box, Karing, Hiddify, mihomo, ClashMeta, FIClash or Surfboard and want a free subscription URL they can paste in, plus a Telegram channel for updates. It does not suit anyone who needs documented uptime guarantees, a support SLA, or a self-hosted setup, because the README publishes links rather than a service contract. Before adopting it, open the permanent subscription URL in a client and confirm it returns a parseable node list, check the Telegram channel at t.me/stymei1 for the current status, and read the repository licence, which is not stated in the repository itself.

Frequently asked questions

Official sources

1. Issues
2. Jsnzkpg/Jsnzkpg on GitHub
3. Project website
4. README
5. Releases