Zygisk Assistant ships v2.1.4 from February 2025 and asks you to turn the deny list off
A Zygisk module to hide root for KernelSU, Magisk and APatch, designed to work on Android 5.0 and above.
At a glance
- What is it?
- Zygisk Assistant is a small C++ Zygisk module whose stated purpose is to hide the existence of root and Zygisk from apps, configured one target app at a time in the root manager. Two things decide whether it is worth installing today: the last tagged release is v2.1.4 from 2025-02-23 while the branch has been pushed to 2026-05-04, and both documented setups ask you to disable a protection rather than to configure one.
- Who is it for?
- Zygisk Assistant suits someone who already runs a root manager, has already turned on Zygisk, and wants root hidden from one specific app rather than from the whole system. It does not suit someone who wants a single global switch, because every part of the setup is scoped to a target app in the manager, and it does not suit someone who wants current code, because the newest release predates the branch by more than a year.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- snake-4/Zygisk-Assistant2,679 ★ · +55
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| snake-4/Zygisk-Assistant | 2.6k | 2.7k |
55 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The hide is scoped to one target app at a time
The module is not a global switch, and the configuration is where that becomes clear. For KernelSU and APatch, the option that has to be enabled is named `Umount modules/Exclude modifications`, and it is enabled for the target app in the KernelSU or APatch Manager, not globally. The Magisk path is built the same way from the other side: the target app is added to the deny list, unless the Magisk fork in use works from a white list instead, in which case the app goes there. So the unit of configuration is one app, chosen in a manager the module does not own, and the same app has to be selected in two different places depending on which root manager is in charge. That also means uninstalling the module does not undo the manager side: the per-app entries are the user's to remove.
Both setups ask you to turn a protection off
Read the two instruction sets side by side and the pattern is consistent. For KernelSU and APatch: install ZygiskNext, enable the umount option for the target app, and disable `Enforce DenyList` in ZygiskNext settings if such a setting exists. For Magisk: optionally update to 27.0 or newer for better hiding capabilities, turn Zygisk on in Magisk settings, turn `Enforce DenyList` off in Magisk settings, and add the target app to the deny list unless a fork with a white list is used. The denylist enforcement is what the module asks you to relax in both cases, and the Magisk note is the only place a version number appears anywhere in the document, with 27.0 recommended rather than required. The phrase if there is one attached to the ZygiskNext setting acknowledges that not every fork exposes it.
The newest release is v2.1.4, published in February 2025
The release list is where the maintenance picture is visible. Three tags appear: v2.1.4 on 2025-02-23, v2.1.3 on 2024-08-17 and v2.1.2 on 2024-08-03, so two of them landed six days apart in August 2024 and the third arrived the following February. The branch has moved since: the last push is dated 2026-05-04, more than a year after the newest tag, and the repository is not archived. That gap matters because the document tells you to use the release build rather than the debug build, and only use debug if you are making a bug report. In practice the recommended build is the February 2025 one, and anything committed since then is only reachable by building from source. No changelog file appears at the root, so what changed between the tag and the branch head is not recorded anywhere in the tree.
A Gradle wrapper in the root and no build command at all
This is a C++ module with a JVM build around it, and the root reflects that: build.gradle.kts, settings.gradle.kts, gradle.properties, a gradle directory, gradlew and gradlew.bat. None of that is explained. The document contains no build command, no required JDK version, no Android SDK level and no native toolchain version, and there is no statement of which NDK the module expects. The top level listing also shows no CMake file and no jni directory, so if a native build description exists it sits inside the module directory where it cannot be seen from the root listing. For a repository whose primary language is C++, that means the build recipe is not written down anywhere a reader can reach, which is the opposite of what the rest of the document does, since the runtime configuration is spelled out option by option.
A .gitmodules file and an update_metadata module
Two entries in the root explain more than the document does. There is a .gitmodules file, so the build pulls at least one dependency as a git submodule rather than as a released package, and nothing in the document names which submodule or why it is not vendored. Then there is update_metadata, sitting beside module as its own Gradle project, which suggests the repository publishes update metadata as a separate artifact rather than only the module zip. Since the module's whole job is to alter what an app sees, a metadata channel is a plausible design for telling an installed module that a new version exists. Neither is described in the text: there is no update channel section, no mention of a submodule, and no list of what the release archives contain.
Android 5.0 and above, with no provider version named
The platform floor comes from the project's own description rather than from the body of the document, which states that the module is designed to work on Android 5.0 and above. The other side of that claim is missing. ZygiskNext is required for the KernelSU and APatch path but no version of it is given, and the Magisk path only mentions 27.0 as an optional improvement for hiding capabilities rather than as a minimum. There is also no statement about which Android versions each root manager itself supports, and no note about what happens on a device where the target app is itself a system app or one with its own integrity checks. The honest summary is that the floor is stated once, the provider requirements are implied by the setup steps, and everything else is left to the person installing it.
Contributing is four git commands and an issue tag
The contribution section is the standard fork workflow, and it is worth quoting exactly because it is the only command sequence in the document:
git checkout -b feature/FeatureName
git commit -m 'Add some FeatureName'
git push origin feature/FeatureNameAlongside it, the suggestion path is an issue tagged enhancement, and the closing line asks for a star. The header links are thinner than they look: Report Bug and Request Feature both point at the same issues page, so the two labels do not filter anything by themselves, and the third link is the releases page. There is no code of conduct, no changelog and no test instructions, and the tree holds a .gitignore, a .gitattributes and a .github directory for the rest of it. For a module this small, that is a reasonable amount of ceremony, but it means the only verification path offered to a contributor is opening an issue.
Editorial conclusion
Zygisk Assistant suits someone who already runs a root manager, has already turned on Zygisk, and wants root hidden from one specific app rather than from the whole system. It does not suit someone who wants a single global switch, because every part of the setup is scoped to a target app in the manager, and it does not suit someone who wants current code, because the newest release predates the branch by more than a year. Before installing, check three things: which root manager you use, since the KernelSU and APatch path needs ZygiskNext while the Magisk path needs the built-in Zygisk toggle; whether you are willing to disable Enforce DenyList in the manager, which both paths ask for; and which build you take, since the release build is recommended and the debug build exists only for bug reports.
Frequently asked questions
What is Zygisk Assistant used for?
It is a Zygisk module whose stated aim is to hide the existence of root and Zygisk from applications. It targets KernelSU, Magisk and APatch, and the hiding is configured per application in the root manager rather than globally.
What is zygisk assistant?
A C++ Zygisk module for KernelSU, Magisk and APatch, described as working on Android 5.0 and above and distributed under the MIT licence. It is installed as a release build rather than launched as an app, and the release build is the one recommended over the debug build.
How do I install zygisk assistant?
Take the release build. For KernelSU and APatch: install ZygiskNext, enable the Umount modules/Exclude modifications option for the target app in the manager, and disable Enforce DenyList in ZygiskNext settings if it exists. For Magisk: optionally update to 27.0 or newer, turn Zygisk on, turn Enforce DenyList off, and add the target app to the deny list unless your fork uses a white list.
How to use zygisk assistant
There is nothing to launch: the module is configured inside your root manager. Pick the target app there, apply the option that hides modules from it, and keep Zygisk itself enabled. Removing the module later does not remove the per-app entries you added in the manager, so those are cleaned up by hand.
zygisk assistant vs zygisk
This repository draws no comparison, because Zygisk is the layer it plugs into rather than an alternative. The KernelSU and APatch path needs ZygiskNext installed, and the Magisk path needs the Zygisk toggle turned on inside Magisk, so in both cases something has to be providing Zygisk before this module has anything to hide.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/snake-4-zygisk-assistant)Star history chart for your README
[](https://hysenlabs.com/projects/snake-4-zygisk-assistant)Was this useful?