RepoPilot

alibaba/AndFix

AndFix is a library that offer hot-fix for Android App.

Mixed

Stale — last commit 5y ago

MixedDependency

last commit was 5y ago; license evidence incomplete…

MixedFork & modify

last commit was 5y ago; license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 5y ago; license evidence incomplete…

  • Stale — last commit 5y ago
  • Concentrated ownership — top contributor handles 59% of recent commits
  • 5 active contributors
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: alibaba/AndFix

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T01:08:28.546Z · commit 0351a4bc38a7

Verdict

Mixed — Stale — last commit 5y ago

  • 5 active contributors
  • CI configured
  • Tests present

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

AndFix is a hot-fix library for Android apps that enables remote patching of bugs without requiring app redistribution. It works by replacing method bodies at runtime using JNI hooks into both Dalvik and ART runtimes, supporting Android 2.3–7.0 across ARM/x86 and 32/64-bit architectures. Patches are distributed as .apatch files and applied immediately via the PatchManager API. Monolithic structure: core Java API in src/ (rooted at com/alipay/euler/andfix/patch/PatchManager.java), native hooking code in jni/ split by runtime type (art/ for ART, dalvik/ for older runtimes) and Android version (art_4_4.h, art_5_0.h, etc.), with compiled .so libraries placed in libs/.…

Start here

Open these first:

  • src/com/alipay/euler/andfix/AndFixManager.java — Core entry point managing patch loading, initialization, and method replacement orchestration—every contributor must…
  • src/com/alipay/euler/andfix/AndFix.java — Public API facade exposing patch management to applications—defines the contract all integrations depend on
  • jni/andfix.cpp — Native layer entry point bridging Java and native method replacement; critical for understanding cross-layer communication
  • jni/art/art_method_replace.cpp — ART runtime method replacement logic—essential for supporting Android 5.0+ devices where most users run
  • jni/dalvik/dalvik_method_replace.cpp — Dalvik runtime method replacement—handles legacy Android 2.3–4.4 versions

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/alibaba/AndFix.git
cd AndFix
./gradlew build

The project uses Gradle wrapper (gradlew). No external services required, but you'll need Android SDK installed. JNI code is pre-compiled into libs/ for ARM and x86.

Daily commands:

./gradlew assembleRelease        # Build AAR library
./gradlew generate*Javadoc      # Generate API docs (see javadoc task in build.gradle)

No traditional "dev server." This is a library; integration is via patchManager = new PatchManager(context); patchManager.init(version); patchManager.loadPatch(); in host app code (see README examples).

Key cautions & unknowns

  • Stale — last commit 5y ago
  • Concentrated ownership — top contributor handles 59% of recent commits
  • 1. NDK version mismatch: jni/Android.mk uses APP_ABI flags that must match your NDK toolchain; mismatched ABIs cause runtime linker errors. 2. Runtime detection fragility: jni/andfix.cpp dispatches to…
  • License evidence is incomplete or ambiguous.
  • Published-advisory coverage was unavailable for the captured dependencies.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Great to learn from" badge

Paste into your README — live-updates from the latest cached analysis.

RepoPilot: Great to learn from
[![RepoPilot: Great to learn from](https://repopilot.app/api/badge/alibaba/andfix?axis=learn)](https://repopilot.app/r/alibaba/andfix)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/alibaba/andfix on X, Slack, or LinkedIn.

Ask AI about alibaba/andfix

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/alibaba/andfix"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>