---

Patch Bundle Registry brings ReVanced, Morphe, and Reseam patch sources together in one searchable catalog. Explore available patches, check app compatibility, and find the right bundle for your manager.

Find your patches

• Search by source, patch name, or description.
• Check compatibility with the package filter. Use an app's package name, such as com.google.android.youtube, an app-version fragment such as 19.16, or an exact combination: [email protected].
• Choose a release using the source, version, bundle format, and release filters.
• Explore a bundle to read its changelog and patch list.
• Browse Apps to see app names, package names, icons, and compatible bundles across matching releases. Names and icons come from cached F-Droid and IzzyOnDroid JSON indexes, then regional Google Play listings; unlisted apps use their package names.

Switch between list and grid views to browse the way you prefer. The address bar follows your tab, filters, and open app or bundle. Copy that URL to share the same view, including a bundle's changelog or historical version. Browser Back and Forward restore previous tabs and details.

Add a bundle to your manager

1. Open the catalog and find a source.
2. Choose a bundle format your manager supports.
3. Click Copy remote bundle URL and paste it into your manager's patch source settings. For Reseam bundles, click the link icon and choose Registry URL (URV) or Reseam Manager JSON.

The default remote URL follows new releases in the selected channel. Select a historical bundle version to copy a URL pinned to that version.

ReVanced formats appear as ReVanced v21 and ReVanced v22. Morphe bundles appear as Morphe. ReVanced v21 and Reseam bundles require their respective runtime plugins when used in URV. The Reseam Manager JSON choice returns the publisher's complete patches.json index with its patch IDs, release history and release notes. The Registry URL choice keeps the existing import format.

You can also download the bundle directly from its card. Available formats and import support depend on the manager you use.

Releases and patch lists

Channel	What you'll find
Latest	The newest release, including prereleases.
Stable	The newest regular release.
Dev	The newest prerelease.

Sources can come from GitHub, GitLab, Codeberg, Gitea and supported self-hosted servers. Some sources do not publish every channel. Select a source to browse indexed bundle versions and their changelogs. Older patch lists may remain missing when their artifacts cannot be extracted.

Patch lists display their status: verified, unverified, stale, or missing. A verified list was extracted from its matching bundle. An unverified or stale list may still help you explore patches, but may not describe the selected release accurately.

API

Building a manager or another integration? The catalog provides a read-only REST and GraphQL API for sources, bundles, patches, and app compatibility. Explore requests in Swagger UI or GraphiQL. Subscribe to catalog changes over WebSockets, or check refresh-job status while an update runs.

Catalog data and history

The catalog indexes patch sources, bundle versions, patch descriptions and options, and app compatibility. Release metadata includes stable/prerelease status, original changelogs, and public asset links. Application names and icons come from cached public listings.

Historical coverage depends on available upstream releases and successful metadata extraction. A recorded release can have a missing patch list, and a saved asset URL may stop working if the publisher removes the download. The registry stores metadata; bundle binaries remain hosted by their publishers.

See the historical API reference for paginated access to release inventories and retained patch/application metadata. Historical endpoints require a deployment with that API enabled; availability is separate from the standard catalog endpoints.

Contribute or get help

Suggest a patch source or report a problem. Include the source's repository URL and a description of what you found. For general questions, visit Discussions.

Pull requests are welcome. See CONTRIBUTING.md.

Credits and license

Thanks to indrastorms for helping automate updates, and brosssh for patch serialization and ReVanced External Bundles, whose website layout this catalog uses.

The project uses the Unlicense. The adapted website files use GPL-3.0-only; see source attribution.