# Aidoku Community Sources: how the unofficial source list works > Aidoku Community Sources is a GitHub-hosted list of unofficial Aidoku sources, added inside the app with one button or one JSON URL. It is convenient, it is community run, and it ships no releases, which is where the sharp edges sit. **Aidoku-Community/sources** — Community-maintained Aidoku sources - Repository: https://github.com/Aidoku-Community/sources - Website: https://aidoku-community.github.io/sources/ - Stars: 604 · Forks: 127 - Language: Rust - License: Apache-2.0 - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/aidoku-community-sources ## Aidoku Community Sources is a list, not a reader Aidoku Community Sources is not an application and it does not read anything on its own. It is a hosted list of source definitions that other people wrote, arranged so that an Aidoku install can pull them in. The project describes them as sources maintained by community members, and the disclaimer states plainly that the project has no affiliation with the content providers or with the Aidoku application itself. That disclaimer does a lot of work for anyone weighing trust. You are adding endpoints that point at third party sites, and neither the Aidoku project nor the providers stand behind them. The top level of the tree holds publishing scaffolding rather than a compiled program: a sources directory, a templates directory, a public directory, rustfmt.toml, CONTRIBUTING.md, both license files and a .github directory. Nothing in that layout resembles something you run on your own machine. The primary language is listed as Rust, but that is for the people authoring sources, not for the people consuming them. ## One Add Repository button adds the whole list on Aidoku 0.7 and newer Consuming this list takes two taps inside Aidoku, provided your version qualifies. The usage notes say that on a device with Aidoku 0.7 or newer installed you can open the published homepage for the project and click the Add Repository button, which registers the source list directly with the app. The button is the intended path for most people. There is no package manager entry, no build step and no Rust toolchain requirement for the reader. Once the list is registered, individual sources can be installed the way Aidoku normally handles them. The version floor is worth dwelling on. If you are running anything older than 0.7, the button flow is not documented for your case and the manual path in the next section is the route the notes describe instead. A related detail the notes leave open is what a refresh does. The button is described as adding the list, not as pinning a version of it, so treat it as a live reference rather than a frozen set. ## The manual route runs through index.min.json in the settings tab Devices where the Add Repository button is unavailable can still point Aidoku at the list by hand. The usage notes describe navigating to the settings tab and, under the source lists page, adding the address https://aidoku-community.github.io/sources/index.min.json. That file is the machine readable form of the same list the homepage serves, and it is the single reference you need if you prefer to manage source lists yourself or if the device you are setting up is locked down by policy. The same address is usable as a source list reference in any setup where you can enter one by hand. One thing the documentation does not spell out is what happens when the list changes underneath you. The notes do not mention pinning a particular copy of index.min.json, and they do not describe a rollback procedure for the list itself. Since the list is served from a web address rather than a versioned release, treat that URL as a live pointer and re-add it deliberately when you want to pick up new entries. ## The issue tracker is the whole maintenance channel Support runs through GitHub issues, not through a desk with stated response times. The usage notes say that if a source is not working, or you want to request a source that is not available in the list, you can create a new issue. There is also a takedown path built for rights holders: if you own a content provider or content hosted on one of the providers a source is offered for and you would rather that source were not listed here, you are asked to contact the maintainers or open an issue, and the project says it will remove it. Two consequences follow. Entries can disappear without notice, because removal is a routine response to a rights request rather than a versioned change. And the burden of checking whether a given source actually works sits with the reader. Nothing published here offers a health score, a last verified timestamp or a list of known broken sources, so a report you file may duplicate one that already exists. ## sources, templates and public: the authoring side of the repository Authoring a source is a separate job from consuming one, and the repository is organized around that split. The top level entries include a sources directory holding the source definitions, a templates directory for new ones, a public directory that backs the published site, and rustfmt.toml, which explains why Rust is the primary language even though no reader ever compiles anything here. Contributors are pointed first at the official Aidoku source development guide for the source format itself, then at CONTRIBUTING.md for the ways to work in this particular repository. That division is worth understanding before you send a pull request: the guide defines the schema and the contributing file defines the local conventions, and they are not the same document. The README says contributions are welcome without naming a maintainer count, and the repository publishes no governance document beyond the two license files and the contribution notes. If you are unsure whether a source belongs here, the issue tracker is the place to ask first. ## Dual Apache-2.0 and MIT licensing covers the definitions, not the content The licensing here is permissive and deliberately dual. The README states that the repository is licensed under either the Apache License, version 2.0, or the MIT license, at your option, and both LICENSE-APACHE and LICENSE-MIT sit at the top level. The contributing terms add a second layer: unless a contributor says otherwise, a contribution intentionally submitted for inclusion in the repository is dual licensed the same way, with no additional terms or conditions. In plain terms, an author can pick either license, and a downstream user can choose the one that suits their own project without asking anyone. MIT is the easier fit for small internal tooling, while Apache-2.0 carries an explicit patent grant, so having the choice removes a negotiation. This describes what the license files grant and is not legal advice. It does not extend to the content the sources point at. A license on a source definition says nothing about rights to what a provider serves, which is the reason the removal process for content owners exists alongside the license files. ## No releases means the served list can change under you The repository is not archived and its last push was on 2026-10-20, so changes are landing and the list is being maintained. That is also where the risk sits. The repository has no GitHub releases, so there is no numbered version of the source list, no changelog to diff and no artifact to roll back to. What changes is the JSON being served. A reader gets whatever index.min.json holds at the moment they add or refresh it, which means a broken entry can appear in an app without any local action and disappear the same way. The project does not publish a release cadence, and a recent push says nothing about how often changes arrive between pushes. For anyone who needs a reproducible source list, that absence is the constraint to plan around, and the sources directory in the repository is where you would look for the underlying definitions if you wanted to pin them yourself. ## Conclusion A reader running Aidoku 0.7 or newer who wants the widest set of community sources gets the most out of this list, and adding it takes one button press or one URL in the settings tab. A reader who needs a pinned, auditable list, or who does not want an unvetted endpoint pointing at a provider, should stay on a small curated set instead. Before you commit, open index.min.json and read the entries you plan to install, confirm the source you rely on is listed and working, and check that your Aidoku build is 0.7 or newer, because the Add Repository flow is not documented for earlier releases. ## FAQ ### What is Aidoku Community Sources and who maintains it? It is a community-maintained list of unofficial sources that are installable in Aidoku, hosted so the app can pull them in. The project states that it has no affiliation with the content providers or with the Aidoku application itself. ### How do I add the Aidoku Community Sources list to Aidoku? With Aidoku 0.7 or newer installed, open the published homepage for the project and click the Add Repository button. Otherwise add https://aidoku-community.github.io/sources/index.min.json from the settings tab, under the source lists page. ### Which license applies to the sources in this repository? The repository is licensed under either the Apache License, version 2.0, or the MIT license, at your option, and contributions are dual licensed the same way unless a contributor says otherwise. The license covers the source definitions rather than the content hosted by the providers those sources point at. ### How do I report a source that is not working or ask for one that is missing? Both go through the issue tracker, which the usage notes point to for a source that fails and for a request to add a source that is not yet listed. A content owner who wants an existing source removed can use the same route. ## Sources - [Aidoku-Community/sources on GitHub](https://github.com/Aidoku-Community/sources) - [Issues](https://github.com/Aidoku-Community/sources/issues) - [License: Apache-2.0](https://github.com/Aidoku-Community/sources/blob/main/LICENSE) - [Project website](https://aidoku-community.github.io/sources/) - [README](https://github.com/Aidoku-Community/sources/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/aidoku-community-sources