# lx-ikun-music-sources: a versioned archive of LX Music and IKUN Music source scripts > The repository is not a player. It is a dated collection of importable source scripts plus links to third-party parsing and paid key services, with a licence that forbids commercial redistribution. **Macrohard0001/lx-ikun-music-sources** — LX_music & IKUN_music 音源收集 - Repository: https://github.com/Macrohard0001/lx-ikun-music-sources - Stars: 2,572 · Forks: 313 - Language: JavaScript - License: NOASSERTION - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/macrohard0001-lx-ikun-music-sources ## What lx-ikun-music-sources actually contains The repository is a collection, not an application. Its README describes the goal as gathering and organising technical resources and information related to music players such as LX Music and IKUN Music, for personal study, research and technical exchange. The top-level layout confirms that reading: dated directories from v260108 through V260817, a folder named files/, a folder for sources shared from ZxwyWebSite, and a folder whose own name explains that custom sources mean using your own account and that there is a risk of account suspension. There is no build system, no package manifest and no server code in the listing. The audience is therefore narrow. You already need an LX Music or IKUN Music client installed, because the repository ships importable scripts rather than playback software. The README points to the upstream projects instead: lx-music-desktop, lx-music-mobile, ikun-music-desktop and ikun-music-mobile, plus lx-netease-music-mobile and phg-music. If you are looking for a player, this is the wrong repository and those links are the right ones. ## How the dated version folders work as a distribution mechanism The release history and the directory names move together. Releases are tagged v260908, v260831 and V260817, and the top level carries matching directories such as V260817, v260724 and v260506. The naming is date-based, so a reader can tell how old a given batch of scripts is without opening it. That is a deliberate choice, and it is more honest than a single mutable folder: when a source breaks, you can see which batch you were on. The cost is duplication. Every dated directory appears to hold its own copy of the relevant scripts, which means a fix in one source does not propagate backwards. The README does not document a changelog per directory, so the difference between v260817 and V260809 has to be inferred from the release titles, which are informal (one is a note about the start of the school term, another mentions a HYWmusic fix). There is no deprecation marker on older folders. A reader who grabs the oldest directory has no in-repo warning that it is stale. The repository is not archived and the last push was on 2026-09-08, so the newest batch is recent. Nothing in the README describes a support window for older batches. ## Installing nothing: importing a source script into your player There is no install step for this repository because it is not software. The README gives no npm, pip or binary installation instructions; it says resources are collected and shared, and directs software users to the upstream player projects. So the practical first use is an import into a client you already have. Start by taking the newest dated directory rather than the repository root, since the root mixes batches. Then open your player's source management screen and import the script file from that directory. The exact menu label depends on the client, and the README does not describe it, so treat the client's own documentation as the authority. For the paid IKUN sources the README gives a different flow: a key is entered on a publish page rather than a file being imported. ```bash # The README lists these import URLs for the paid Linglan sources. # Replace the placeholder with the key you bought from the third party. https://source.shiqianjiang.cn/api/script/lx?key=你的卡密 https://lc.guoyue2010.top/script/lx?key=你的卡密 https://lx.xiagua.top/script/lx?key=你的卡密 ``` Those three URLs are the only concrete endpoints the README supplies for paid sources. It also names two shop domains, shop.guoyue2010.top and shop.shiqianjiang.cn, and for IKUN sources a publish page at publish.ikun0014.top plus a purchase page at shop.ikunshare.com. The README states that the IKUN sources support LX Music and its modified builds, CyMusic, MusicFree (with support ending soon) and two downloader package names, com.ikunshare.music.downloader and com.mylrc.mymusic, and that users in regions with strong network restrictions must use an IP-based version. ## The third-party services are the real risk surface The README separates its own content from everything else with explicit warnings, and the separation is worth taking literally. The online parsing services are described as third-party and unrelated to the project, with stability and security left to the user's own judgement. The six parsing URLs listed, including wyapi.toubiec.cn, mscdownload.pages.dev and jx.chksz.top, are exactly that: endpoints operated by someone else, with no stated uptime commitment. The paid sources carry the same disclaimer plus their own terms. Those terms say the sources are for testing only, that users should delete related caches within 24 hours, and that keys must not be forwarded or resold at a markup. Prices are listed per tier, from a daily key up to a permanent one. None of this is enforced by the repository, and the README says any consequences are unrelated to it. The folder for custom sources is the clearest limitation in the whole listing. Its name states that you supply your own account, otherwise you cannot listen, and that there is a probability of account suspension. That is a real failure mode, stated by the project itself, and it applies to the approach rather than to a single script. If losing a music account matters to you, that folder is not for you. The README also makes no stability or security guarantee at all, in its own words, and disclaims responsibility for the consequences of use. Read that as the maintainers declining to support what the scripts do once loaded. ## How this differs from running your own LX Music API server A common alternative is to run a self-hosted API server for LX Music, which is a different kind of thing entirely. A server is software you deploy and operate: you control the process, you see its logs, and you decide which upstream endpoints it talks to. This repository is the opposite arrangement. It hands you scripts and links that depend on machines other people run, and when one of those machines changes behaviour, the fix arrives as a new dated directory rather than as a patch you apply. The trade-off is effort against control. Running a server means owning deployment, updates and network exposure. Importing a script means accepting that the endpoint behind it may change without notice and that your only recourse is to wait for the next batch or switch to another source in the list. The README's collection model assumes you will switch: it lists many sources, several parsing sites and multiple import URLs for the same paid product, which reads as redundancy by design. The repository also points at CeruMusic and notes that it has been archived. That is a useful signal about the shelf life of projects in this corner of the ecosystem, and it is the kind of fact a source list should carry. ## Licence, maintenance and what upgrading costs you The licence field reports NOASSERTION, and the README explains why. It says the project is bound by a custom licence, referred to as the simple Macrohard licence, and that commercial use or unauthorised re-upload is forbidden without explicit permission. The README spells out examples: reposting to platforms that generate revenue, selling, embedding into a commercial product, or using it to provide a paid service. Personal, non-commercial exchange is permitted with attribution, and the README directs readers to LICENSE.md for the full terms. That file is the authority, not this summary, and nothing here is legal advice. Maintenance looks regular rather than dormant: the last push was on 2026-09-08 and releases appeared on 2026-08-31 and 2026-08-17. The README also notes that the repository is now maintained jointly by two people, and it mentions donations and a QQ contact for contributions. None of that implies a support commitment. Upgrade cost is manual and repetitive. Because each batch is a dated directory, staying current means re-importing from the newest folder whenever a source stops working, and checking whether the script you used has been replaced rather than fixed. There is no migration guide and the README does not document rollback, so keeping your previous working directory is the only fallback the repository supports. ## Conclusion Adopt this repository only as a personal, non-commercial index of source scripts for LX Music or IKUN Music, and only if you accept that every paid or online parsing service listed is third-party and outside the maintainers' control. Do not adopt it if you need a player, a stable API, or anything you can ship inside a commercial product: the licence forbids commercial use and resale, and the README states the project offers no stability or security guarantee. Before importing anything, open the newest dated directory, read LICENSE.md in full, and check whether the specific script you want points at a paid key or a public endpoint. ## FAQ ### Is lx-ikun-music-sources a music player I can install? No. The README describes it as a collection of resources and information for players such as LX Music and IKUN Music, and the repository holds dated folders of source scripts rather than application code. To play music you need one of the clients the README links to, such as lx-music-desktop or ikun-music-mobile. ### Which folder of lx-ikun-music-sources should I import from? Use the newest dated directory, since the top level mixes batches and the release history moves with those folder names. The README does not document a per-directory changelog, so the difference between batches has to be inferred from the release titles. ### Are the paid sources and online parsing links part of lx-ikun-music-sources? No. The README states that the online parsing services and the paid sources are third-party, not developed or maintained by the project, and that stability, security and any consequences are the user's own responsibility. The paid sources also carry their own terms, including a 24-hour cache deletion instruction and a ban on reselling keys. ### Can I use lx-ikun-music-sources in a commercial product? The README says commercial use and unauthorised re-upload are forbidden without explicit permission, giving selling, embedding into a commercial product and providing a paid service as examples. It points to LICENSE.md for the full terms, and the repository's licence field is reported as NOASSERTION. ## Sources - [Issues](https://github.com/Macrohard0001/lx-ikun-music-sources/issues) - [Macrohard0001/lx-ikun-music-sources on GitHub](https://github.com/Macrohard0001/lx-ikun-music-sources) - [README](https://github.com/Macrohard0001/lx-ikun-music-sources/blob/main/README.md) - [Releases](https://github.com/Macrohard0001/lx-ikun-music-sources/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/macrohard0001-lx-ikun-music-sources