Androguard
v4.1.4 open-sourceThe section your link pointed to isn't on Androguard's page any more, so we've brought you to the top.
Androguard is a Python toolkit for Android reverse engineering: inspect APKs, disassemble or decompile DEX code, and hunt references and vulnerabilities.
androguard cg app.apk
from androguard.core.axml import AXMLPrinter
axml = AXMLPrinter(data)
if axml.is_valid():
print("Valid AXML")
from androguard.core.analysis import analysis
cls = analysis.ClassAnalysis(class_node)
print(cls.get_parent_class())
print(cls.get_interfaces())
androguard apkid my_app.apk
Summary
Androguard is an open-source reverse-engineering tool, written in Python, for working with Android files, parsing APK, DEX/ODEX, binary XML and resources, and disassembling or decompiling bytecode. It runs as a command-line tool with an accompanying GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands., and can also be imported as a library for custom analysis scripts, with optional Frida support for dynamic analysis. This puts it in the hands of reverse engineers and malware analysts examining Android applications rather than teams doing broad mobile app security testing. The README lists projects like Cuckoo Sandbox and AppKnox built on top of it, positioning it as infrastructure other Android analysis tools depend on rather than a standalone scanner. First committed in 2010 and still actively maintained, with 136 contributors and a release 77 days ago.
Androguard is a Python toolkit for Android reverse engineering: inspect APKs, disassemble or decompile DEX code, and hunt references and vulnerabilities.
How Androguard helps
What permissions and components does this APK actually declare and use, once the manifest is decoded?
parses the binary XML AndroidManifest directly and prints it in readable form, listing permissions, activities, services and receivers without needing the original source
Is this APK signed the way it claims to be, and by whom?
reads the v1/v2/v3 signing blocks and certificate data directly from the APK and prints the certificate fingerprints and signer details
What do the raw resource and string tables in this app actually contain?
parses the resources.arsc table and compact entries directly, resolving resource IDs to their values without launching the app
How do these hundred APKs compare against each other for triage?
runs the same parsing and analysis session across a directory of samples and stores the results in a database so they can be queried together instead of one file at a time
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Androguard, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Androguard puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
9 entries
No entries match these filters.
- June 20261
- February 20251
- May 20241
- February 20241
- December 20231
- January 20192
- March 20181
- February 20181
Project health
Issue, contributor and maintainer activity in androguard/androguard, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −6 vs prior 12 months
- Maintainers 1 +1 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 10 days first maintainer reply 12 days
- Open backlog 39 of 649 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 39
- Contributors / month 1
- Commits / month 11
- Stars 6,257
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →