dr-tsng/zygisknext

Standalone implementation of Zygisk

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 5th, 2026
Created on January 28th, 2023
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 638
Total Stargazers: 10,563 (+1)
Total Subscribers: 102 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.5 hours
Mean response time: 3.2 days
90th percentile: 5.2 days
Tracked items: 166

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 13% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 3
Closed in 7 days: 2
Avg open age: 6 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (69)
  • invalid (19)
  • enhancement (17)
  • spam (10)
  • upstream (4)
  • duplicate (2)
  • module issue (1)
  • stupid (1)

Detailed Description

Zygisk Next is a standalone implementation of Zygisk that provides Zygisk API support for KernelSU and serves as a replacement for Magisk's built-in Zygisk functionality.

The tool addresses the need for process injection capabilities on Android systems running KernelSU or Magisk without relying on each root manager's native Zygisk implementation. It works by providing a standalone Zygisk runtime that can inject code into init-oriented processes, exposing an API through which modules can hook into application lifecycle events. The project also supports application callbacks for HyperOS Rust Runtime as a native-only API distinct from standard Zygisk module compatibility.

Adoption requires meeting specific version minimums: KernelSU users need at least version 10940 with ksud at 11575 or higher, while Magisk users require version 26402 with built-in Zygisk disabled. The tool is incompatible with systems running multiple root implementations simultaneously. Developers building modules for this implementation can reference the provided API header and sample module repository for integration patterns. The project maintains a translation contribution workflow through a dedicated branch for WebUI localization.

The project shows active maintenance with ongoing development and documentation updates. The codebase includes comprehensive API documentation and example implementations to guide module developers. The team has established clear licensing terms and contribution guidelines, including a dedicated translation workflow that accepts community contributions.