Best Mihon Extension Repo List: GitHub Repositories & Fixes 2026

An overview of how Mihon connects to third-party extension repositories.

A Mihon extension repo list is a directory of the third-party repositories that can supply extension catalogs to Mihon and compatible apps. People search for one because the names and links do not line up. One guide points to Keiyoushi, another to a Yuzono URL, a third to a fork nobody recognises, and some GitHub pages that look relevant turn out to be ordinary source code with no catalog behind them.

This Mihon extension repo list is a discovery directory, not a setup tutorial. Below you will find a factual table of repositories that can be checked on GitHub, an explanation of repository types (independent, downstream, fork, mirror, archived), a method for telling a real repository from a plain GitHub page, and a checklist for judging whether one is still current. Nothing here is ranked. For app basics, see the Mihon app guide; for adding a repository, use the Mihon extensions guide. The app itself is developed openly in the mihonapp/mihon repository on GitHub.

Mihon Extension Repo List Terms: Repo vs Extension Store

Searches still use “Mihon extension repo,” but the app itself has changed its wording. The Mihon v0.20.0 release notes state that the terms “extension repo” and “obsolete” were changed to “extension store” and “orphaned.” If you use an older build, you may still see the old label; on newer builds you will see the new one.

The two phrases refer to the same thing: a URL that points to a metadata index describing which extension packages exist. That index is not the extensions themselves, and it is not Mihon. In this Mihon extension repo list, “repository” and “store” are used interchangeably, and “repository” is kept where it matches how people search.

Eight Terms You Will See in Any Mihon Extension Repo List

For a wider look at extensions themselves, our Tachiyomi extensions guide covers what individual packages do.

Mihon Extension Repo List for 2026: Verified GitHub Repositories

The Mihon extension repo list below only includes projects whose GitHub pages could be read while writing this article. Statuses reflect what those pages showed on September 29, 2026, and can change. “Type” describes how the project relates to others, not its quality. Raw index URLs are given only where a project’s own README states them; for everything else, copy the link from the current README.

Third-party repositories can be independent, downstream, forked, mirrored or specialised.

Keiyoushi in the Mihon Extension Repo List

Keiyoushi is the repository most guides start with. It is hosted on GitHub under the keiyoushi organisation. The catalog lives in keiyoushi/extensions, whose About line describes it as an extension repository for Mihon and variants, and the Kotlin code that builds extensions lives separately in keiyoushi/extensions-source. Issues and source requests are handled in the source repository.

It is a third-party project, not part of Mihon. Its own README says it is not affiliated with Mihon or Tachiyomi and asks users not to seek help for these extensions through Mihon’s support channels. Its README also points to a Keiyoushi website with an add-to-app flow and a manual listing page.

One detail worth noticing: the current README on the repo branch lists an index.pb URL, while many older guides show an index.min.json link. Mihon v0.20.0’s notes mention support for a newer extension index format, so the file type your build accepts can matter. Always copy the link from the current README rather than from a screenshot. If you are on an older app build, our Tachiyomi old version page explains what changes between releases.

For step-by-step setup, use the setup guides linked at the start of this article.

Other Repositories in the Mihon Extension Repo List

Yuzono manga-repo. The project README says its catalogs are compatible with Komikku and Mihon or other forks, and that it automatically merges Keiyoushi updates every six hours while adding a small number of its own extensions and improvements. That makes it a downstream repository, not a fully separate catalog. It also states it is not affiliated with Komikku, Mihon or Tachiyomi. The README advises using the yuzono/manga-repo URL even when copies of the project exist under other GitHub accounts, which is a good example of mirrors and forks appearing in search results. Komikku and other apps that use these repositories are compared in the Tachiyomi forks guide.

Yuzono cursed-manga-repo. Yuzono’s organisation also lists cursed-manga-extensions as source code for Komikku, Mihon and forks. A forked copy of its catalog README tells users to keep using the yuzono/cursed-manga-repo URL. Its scope is not the same as the main repo, so read the README before adding it.

Mihonyomi. This repository is aimed at self-hosted servers. Its README says compiled APKs sit in a releases branch and source on main, warns that closed-source extensions and fake compatible readers have appeared, and says it was made for the author’s own Komga use. It points Kavita users to Kavita’s own extension instead.

Filtered forks. MiguelMA3/mihon-extensions describes itself as a filtered fork of Keiyoushi that removes listed content through a workflow before generating index files, and warns that it is unofficial and modified. It is clearly a fork, and its catalog is a subset of the original.

Archived projects. tachiyomi-extensions-revived is archived and asks users to migrate to Keiyoushi. It remains a useful case study: old links found in older tutorials can point to projects that no longer accept updates.

Mihon Extension Repo List: How GitHub Sources Work

GitHub is the usual host because it gives free file hosting, automated builds, public history and an issue tracker. A repository maintainer typically builds packages with GitHub Actions and publishes them, along with an index file, on a dedicated branch. Users then add a raw link to that index in the app.

That means a GitHub page is not automatically an extension repo. When you land on one, look for:

• README: does it describe itself as an extension repository and say which apps it supports?
• Index files: is there a published index.min.json, index.json or index.pb, usually on a repo or releases branch?
• Release or branch history: is the metadata branch updated regularly?
• Issues: are reports answered, closed or ignored?
• Commits and activity: when was the last meaningful change?
• Ownership: is the account or organisation the same one the README links to?

GitHub repositories can publish the metadata required by compatible Mihon clients.

Mihon Extension Repo List Beyond Keiyoushi

Readers asking for a Mihon extension repo other than Keiyoushi usually want to know what else exists and whether it is different. Based on the projects in this Mihon extension repo list, the honest answer is that most alternatives are related to Keiyoushi in one way or another.

Whether their catalogs differ in practice is something only the current index can show, so this article does not claim which extensions any repository contains. Before adding one, verify who maintains it, when it was last updated, whether it lists your app as supported, and whether its README explains what was added or removed. Two repositories that carry the same extension can create duplicate entries, so add only what you need. If you are after sources to install rather than repositories to compare, see the best Tachiyomi extensions list.

Mihon Extension Repo List Links: How to Verify a Repository URL

Many failed links come from copying the wrong kind of URL. These five look similar but do different jobs:

Short checklist: get the link from the maintainer’s README; confirm the owner name matches; confirm it ends in an index file the README mentions; check the file loads in a browser as data rather than a web page; and compare the branch name to the README. If a tutorial and a README disagree, trust the README. Setup itself is covered in the Tachiyomi extension repo guide.

How to Evaluate Any Mihon Extension Repo List Entry

Instead of asking which repository to pick, ask whether a given repository passes a basic review. These ten checks apply to every project in the Mihon extension repo list, and to any new one you find later.

Use these checks to evaluate a third-party Mihon extension repository.

1. Clear repository owner. A named person or organisation, with a consistent link from README to profile.
2. Current maintenance. Recent commits and metadata updates, not a last change from years ago.
3. Mihon compatibility. The README says which apps it supports, and the index format suits your build.
4. A clear README. It explains what the repository is, who runs it and what it contains.
5. Valid metadata. A published index file that loads without error.
6. Transparent source code. Public build code, ideally with an open-source license, so packages can be traced back to source.
7. Issue tracking. Issues enabled and being handled, so problems have somewhere to go.
8. Update history. A visible record of what changed and when.
9. Clear installation instructions. A README that names the exact link to use, so you are not guessing.
10. Security considerations. Mihonyomi’s README warns that closed-source extensions and fake compatible readers have appeared. Prefer open source, be cautious with unexplained packages, and check what the trust prompt shows.

Are Mihon Extension Repositories Official?

Mihon is the application. The repositories in this Mihon extension repo list are separate projects run by other people. Keiyoushi’s README says it is not affiliated with Mihon or Tachiyomi, and Yuzono’s README says the same about Komikku, Mihon and Tachiyomi. Mihon’s changelog describes support for extension formats, but that is not an endorsement of any specific repository.

So the practical position is: no third-party repository should be treated as an official Mihon product unless Mihon’s own documentation says so. Check ownership on GitHub yourself, and treat labels like “official” on other websites as claims to verify. These repositories are built for Android apps; iPhone readers should look at the Tachiyomi for iOS page instead.

Mihon Manga Extension Repo vs Anime Extension Repo

A Mihon manga extension repo generally lists extensions for reading manga, comics and similar content. Anime extensions belong to a different ecosystem. The Yuzono organisation, for example, lists aniyomi-extensions as separate source code for Anikku, Aniyomi and forks, distinct from its Komikku and Mihon repository.

The point is not to explore Aniyomi here. It is to avoid assumptions: a link that works in a Mihon-compatible app does not mean the repository has anime content, and searches for a “Mihon anime extension repo” can lead to projects meant for other apps. Read the README, look at the app names it lists, and confirm the content type before adding it. If you are weighing different reader apps altogether, see the Tachiyomi alternatives page, and find more guides on the TachiYomiTips home page.

What If a Mihon Extension Repo List Entry Is No Longer Available?

• The URL may have changed. Projects get renamed or moved. Yuzono’s README, for instance, advises keeping one specific URL regardless of where the GitHub repository sits.
• The project may be archived. An archived repository is read-only; the README often names a successor.
• Metadata may be gone. A deleted branch or index file leaves a link that returns an error.
• Forks may exist. Treat them as separate projects with their own owners and check each one.

Start with the project’s current README and recent activity. For extension-level problems, see the fix extensions not working guide, and if adding a link returns a 404, read the Tachiyomi error 404 fix.

Mihon Extension Repo List: Frequently Asked Questions