ax/apk.sh

Makes reverse engineering Android apps easier, automating repetitive tasks like pulling, decoding, rebuilding and patching an APK.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 18th, 2026
Created on September 22nd, 2022
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 228
Total Stargazers: 3,833 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.1 days
Mean response time: 39.5 days
90th percentile: 151.0 days
Tracked items: 5

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

apk.sh is a shell script that automates the reverse engineering workflow for Android applications.

The tool addresses the tedium of repeatedly pulling APK files from devices, decompiling them, modifying code or resources, and repackaging them for testing. It wraps common reverse engineering tasks into a streamlined command-line interface, handling the orchestration of tools like apktool for decoding and rebuilding, along with integration points for Frida instrumentation and Objection for runtime analysis. This automation eliminates manual steps that would otherwise consume significant time during iterative analysis and patching cycles.

The project suits developers and security researchers who regularly work with Android application internals, particularly those performing dynamic analysis, vulnerability research, or app modification. It is most valuable when you need to repeatedly cycle through the decode-modify-rebuild loop rather than performing one-off analysis. The tool assumes familiarity with Android reverse engineering concepts and the underlying tools it orchestrates.

Development activity shows consistent engagement with the codebase through regular commits addressing bugs and feature requests. The project maintains responsiveness to user-reported issues and incorporates feedback into updates. Maintenance appears focused on keeping the automation reliable as underlying tools and Android versions evolve, with attention to edge cases that arise from real-world reverse engineering scenarios.