[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73185":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":35,"readmeContent":36,"aiSummary":37,"trendingCount":16,"starSnapshotCount":16,"syncStatus":38,"lastSyncTime":39,"discoverSource":40},73185,"ReZygisk","PerformanC\u002FReZygisk","PerformanC","Transparent implementation of Zygisk.","",null,"C",3591,338,41,3,0,15,35,128,45,29.59,"GNU General Public License v3.0",false,"main",true,[27,28,29,30,31,32,33,34],"android","apatch","injection","kernelsu","magisk","root","zygisk","zygote","2026-06-12 02:03:10","# ReZygisk\n\n[Español(Argentina)](\u002FREADMEs\u002FREADME_es-AR.md)|[Bahasa Indonesia](\u002FREADMEs\u002FREADME_id-ID.md)|[Português Brasileiro](\u002FREADMEs\u002FREADME_pt-BR.md)|[Українська](\u002FREADMEs\u002FREADME_uk-UA.md)|[Tiếng Việt](\u002FREADMEs\u002FREADME_vi-VN.md)|\n\nReZygisk is a fork of Zygisk Next, a standalone implementation of Zygisk, providing Zygisk API support for KernelSU, APatch and Magisk.\n\nThe codebase has been rewritten to C entirely, bringing not only a much cleaner codebase that is easier to follow, but also a lighter binaries that are also faster. Custom linkers also have been introduced to future-proof ReZygisk against future detections, not using system linker at all in normal circunstances, defeating any linker-based detection.\n\n## Why?\n\nThe latest releases of Zygisk Next are not open-source, reserving entirely the code for its developers. Not only does that limit our ability to contribute to the project, but also impossibilities the audit of the code, which is a major security concern, as Zygisk Next is a module that runs with superuser (root) privileges, having access to the entire system.\n\nThe Zygisk Next developers are famous and trusted in the Android community, however, this doesn't mean that the code is not malicious or vulnerable. We (PerformanC) understand they have their reasons to keep the code closed-source, but we believe the contrary.\n\n## Advantages\n\n- FOSS (Forever)\n\n## Dependencies\n\n| Tool            | Description                            |\n|-----------------|----------------------------------------|\n| `Android NDK`   | Native Development Kit for Android     |\n\n### C Dependencies\n\n| Dependency  | Description                   |\n|-------------|-------------------------------|\n| `PLTI`      | Simple PLT Hook for Android   |\n| `CSOLoader` | SOTA Linux custom linker      |\n\n## Installation\n\n### 1. Select the right zip\n\nThe selection of the build\u002Fzip is important, as it will determine how hidden and stable ReZygisk will be. This, however, is not a hard task:\n\n- `release` should be the one chosen for most cases, it removes app-level logging and offers more optimized binaries.\n- `debug`, however, offers the opposite, with heavy logging and no optimizations, For this reason, **you should only use it for debugging purposes** and **when obtaining logs for creating an Issue**.\n\nAs for branches, you should always use the `main` branch, unless told otherwise by the developers, or if you want to test upcoming features and are aware of the risks involved.\n\n### 2. Flash the zip\n\nAfter choosing the right build, you should flash it using your current root manager, like Magisk or KernelSU. You can do this by going to the `Modules` section of your root manager and selecting the zip you downloaded.\n\nAfter flashing, check the installation logs to ensure there are no errors, and if everything is fine, you can reboot your device.\n\n> [!WARNING]\n> Magisk users should disable built-in Zygisk, as it will conflict with ReZygisk. This can be done by going to the `Settings` section of Magisk and disabling the `Zygisk` option.\n\n### 3. Verify the installation\n\nAfter rebooting, you can verify if ReZygisk is working properly by checking the module description in the `Modules` section of your root manager. The description should indicate that the necessary daemons are running. For example, if your environment supports both 64-bit and 32-bit, it should look similar to this: `[Monitor: ✅, ReZygisk 64-bit: ✅, ReZygisk 32-bit: ✅] Standalone implementation of Zygisk.`\n\n## Translation\n\nThere are currently two different ways to contribute translations for ReZygisk:\n\n- For translations of the README, you can create a new file in the `READMEs` folder, following the naming convention of `README_\u003Clanguage>.md`, where `\u003Clanguage>` is the language code (e.g., `README_pt-BR.md` for Brazilian Portuguese), and open a pull request to the `main` branch with your changes.\n- For translations of the ReZygisk WebUI, you should first contribute to our [Crowdin](https:\u002F\u002Fcrowdin.com\u002Fproject\u002Frezygisk). Once approved retrieve the `.json` file from there and open a pull request with your changes -- adding the `.json` file to the `webroot\u002Flang` folder and your credits to the `TRANSLATOR.md` file, in alphabetic order.\n\n## Support\n\nFor any question related to ReZygisk or other PerformanC projects, feel free to join any of the following channels below:\n\n- Discord Channel: [PerformanC](https:\u002F\u002Fdiscord.gg\u002FuPveNfTuCJ)\n- ReZygisk Telegram Channel: [@rezygisk](https:\u002F\u002Ft.me\u002Frezygisk)\n- PerformanC Telegram Channel: [@performancorg](https:\u002F\u002Ft.me\u002Fperformancorg)\n- PerformanC Signal Group: [@performanc](https:\u002F\u002Fsignal.group\u002F#CjQKID3SS8N5y4lXj3VjjGxVJnzNsTIuaYZjj3i8UhipAS0gEhAedxPjT5WjbOs6FUuXptcT)\n\n## Contribution\n\nIt is mandatory to follow PerformanC's [Contribution Guidelines](https:\u002F\u002Fgithub.com\u002FPerformanC\u002Fcontributing) to contribute to ReZygisk. Following its Security Policy, Code of Conduct, and syntax standard.\n\n## License\n\nReZygisk is licensed under [AGPL 3.0](.\u002FLICENSE). You can read more about it on [Open Source Initiative](https:\u002F\u002Fopensource.org\u002Flicenses\u002FAGPL-3.0).\n","ReZygisk是一个透明实现Zygisk的开源项目，旨在为KernelSU、APatch和Magisk提供Zygisk API支持。该项目使用C语言完全重写了代码库，使得代码更加简洁易懂，同时生成的二进制文件更轻量且运行速度更快。此外，ReZygisk引入了自定义链接器以应对未来可能出现的检测机制，通常情况下不使用系统链接器，从而绕过基于链接器的检测。此工具适用于需要对Android设备进行高级定制或安全增强的场景，如开发者希望在保持root权限的同时增加系统的安全性与稳定性。",2,"2026-06-11 03:44:25","high_star"]