A ROOT REQUIRED LSPosed/Zygisk module to hide your app list, settings, package installers and more. It is a fork of Hide My Applist project.
2.4k
Stars
179
Forks
2
Open issues
28
Contributors
AI Analysis
HMA-OSS is a Kotlin-based LSPosed/Zygisk module for rooted Android devices that hides app lists, settings, and package installers to prevent apps from detecting root-related tools or using app lists for fingerprinting. It serves a specialized security niche: Android power users and developers who need to conceal root installation markers from detection-sensitive applications, not general users or app developers.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Kotlin Xposed/Zygisk module forking Hide My Applist to obscure installed apps from detection and fingerprinting
HMA-OSS is a rooted Android module enabling app list obfuscation and detection evasion, primarily targeting users who need to hide root-detection tools or prevent app fingerprinting. It forks the earlier Hide-My-Applist project and distributes via Xposed/Zygisk injection. The project attracts a narrow, technically proficient user base concerned with privacy or security tool concealment. Real-world adoption evidence remains limited to GitHub metrics and distribution channels; institutional or corporate deployment is not documented.
Created September 2025 as an explicit fork of Hide-My-Applist (Dr-TSNG), HMA-OSS appears to modernize or provide an alternative distribution path for app-hiding functionality in the rooted Android ecosystem. The fork model suggests either divergent maintenance priorities or licensing concerns relative to the original project.
The project gained 85 stars in the prior 7 days (as of 2026-06-29), placing it on a trajectory toward ~4,400 stars annually if sustained. This growth rate sits between the original Hide-My-Applist (5,359 stars) and smaller competitors like KnoxPatch (1,445 stars), suggesting modest but steady interest among the Xposed/Zygisk user community. Presence on IzzyOnDroid and Rbtlog distribution channels (noted in README badges) indicates recognition within privacy-focused Android circles.
Adoption not verified. GitHub stars, fork count, and CI/CD activity indicate technical interest, but no user counts, deployment case studies, penetration data, or downstream integration documentation are present. Distribution via IzzyOnDroid and Rbtlog suggests real usage among privacy-aware Android users, but scale is opaque. Presence of Telegram channel suggests an active community, but membership and engagement metrics are not publicly visible.
Likely implements Xposed/Zygisk hooks to intercept package-listing and app-detection APIs at the system level. Based on README, it targets app list visibility, settings access, and package installer interactions. No architectural details, dependency structure, or module interfaces are described in the README excerpt; implementation complexity and hook reliability cannot be assessed from available documentation.
Not documented in README. No mention of automated testing, CI/CD test workflows, or integration test strategy. Metadata shows active CI/CD workflow status badge, but test scope and pass rates are not disclosed.
Very recent: last push 2026-06-29 (same day as evaluation date), indicating active ongoing development. CI/CD workflow badges present suggest automated build/deployment. No issue response time, PR merge velocity, or maintainer availability metrics are provided. Rapid star growth (85 in 7 days) suggests community engagement. Maintenance frequency appears consistent but depth of active issue triage is not documented.
ADOPT IF: you run a rooted Android device (Xposed or Zygisk framework), need to hide root-detection tools to bypass app-store or banking restrictions, or seek fingerprint evasion for privacy. You are comfortable with AGPL-3.0 licensing and active maintenance on a rapidly evolving fork. AVOID IF: you require stable, long-term API commitments, extensive production documentation, or SLA guarantees. Avoid if you need non-rooted solutions or cannot accept potential breakage across Android updates or framework patches. MONITOR IF: you depend on app hiding at scale or in critical security contexts—adoption evidence is not yet sufficient to assess real-world reliability or incident response.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Fork dependency: HMA-OSS relies on active maintenance of upstream Xposed/Zygisk frameworks. API changes in those frameworks could break the module without warning; maintainer capacity to respond is not documented.
- Root requirement creates security boundary: Users must trust the module and framework with system-level access. Malicious or vulnerable code could compromise the entire device.
- Adoption not verified at scale: Incident reports, performance issues, or compatibility problems may exist but are not visible in public repositories or issue trackers; real-world failure modes are unknown.
- AGPL-3.0 licensing: Derivative works must remain open-source and GPL-compatible. Commercial or proprietary integrations may face legal friction.
- Rapid star growth may not reflect sustainable engagement: Week-over-week volatility could reverse; star count is a weak proxy for production deployment or long-term community trust.
HMA-OSS will likely remain a viable alternative within the Xposed/Zygisk ecosystem for 12–24 months if maintenance continues at current pace. Mainstream adoption is improbable given the rooted-only requirement and narrow use case. The project may merge back into or be superseded by the original Hide-My-Applist if the fork's differentiation (maintenance, licensing, or features) does not solidify. Android OS updates and Google Play policy shifts toward anti-rooting enforcement could gradually erode user base.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Kotlin
- License
- AGPL-3.0
- Last updated
- 20h ago
- Created
- 10mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Open pull requests
Similar repos
Dr-TSNG/Hide-My-Applist
Hide My Applist is an Xposed module that intercepts and blocks app list...
deltazefiro/Amarok-Hider
Amarok-Hider is an Android privacy application that hides files and apps...
salvogiangri/KnoxPatch
KnoxPatch is an LSPosed module that restores Samsung Knox-dependent apps and...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
frknkrc44/HMA-OSS
this
|
2.4k | +67 | Kotlin | 7/10 | 20h ago |
|
Dr-TSNG/Hide-My-Applist
|
5.4k | — | Kotlin | 8/10 | 9mo ago |
|
deltazefiro/Amarok-Hider
|
3.1k | — | Java | 7/10 | 1w ago |
|
salvogiangri/KnoxPatch
|
1.5k | — | Kotlin | 7/10 | 2d ago |
 aistra0528/Hail
|
6.2k | — | Kotlin | 8/10 | 4d ago |
 LSPosed/AndroidHiddenApiBypass
|
2.4k | — | Java | 8/10 | 1mo ago |
Direct predecessor with ~2.4× higher star count (5,359 vs 2,267). HMA-OSS appears to be a maintained fork; competitive positioning (maintenance improvements, licensing clarity, or distribution access) is not explicitly documented in README.
Larger ecosystem player (~6,052 stars). Likely offers broader app management features beyond app list hiding; HMA-OSS appears more focused on anti-detection and fingerprinting resistance.
Similar star count (3,114 stars). Comparable functional scope; relative maintenance and feature completeness cannot be determined from README alone.
Smaller niche (1,445 stars). Likely targets Samsung Knox-specific scenarios; narrower scope than HMA-OSS's broader app concealment approach.
