deps-audit

Inventory bundled third-party libraries in Android APKs and map versions to known CVEs.

48|27|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/abisheikM1/Tribunal --skill deps-audit-abisheikm1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deps-audit
Source: https://github.com/abisheikM1/Tribunal/tree/main/legacy-harness/skills/deps-audit
Command: npx skills add https://github.com/abisheikM1/Tribunal --skill deps-audit-abisheikm1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Android apps bundle dozens of third-party SDKs whose known vulnerabilities become the app's attack surface, but manually identifying every bundled library and checking its version against CVE feeds is slow and error-prone. This Skill automates the inventory of native libraries, SDK package roots, and version metadata so you can quickly map shipped dependencies to known vulnerabilities. ## Core Features & Use Cases - Bundled Library Inventory: Scans extracted APK directories for native .so libraries (with ABI), third-party SDK smali package roots matched against a built-in signature map (OkHttp, Play Core, Jackson, Facebook, AppsFlyer, and more), and version-hint files like pom.properties and BuildConfig. - CVE Lookup Guidance: Prints OSV, NVD, and GHSA search URLs for every detected SDK so you can confirm the shipped version against live advisory feeds. - Tracker PII Detection: Flags analytics and attribution SDKs (Facebook, AppsFlyer, Adjust, Branch, Flurry) for follow-up dynamic observation of PII exfiltration over Burp or mitmproxy. - Use Case: During an authorized Android pentest, run the inventory script against a decompiled target to discover the app bundles Google Play Core 1.7.1, then confirm CVE-2020-8913 on NVD and hand the code-execution analysis to a companion exploitation skill. ## Quick Start Ask the agent to inventory the bundled third-party libraries and SDKs in the extracted APK under targets/<hash> and list which ones have known CVEs.

Frequently Asked Questions about deps-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find vulnerable dependencies in an Android APK?

Run the inventory script against the extracted APK directory to list bundled SDKs, native .so libraries, and version-hint files. Then identify the exact shipped version from pom.properties or BuildConfig and check it against OSV, NVD, or GHSA feeds using the URLs the script prints.

How to generate an SBOM for an Android app?

The inventory script produces a first-pass software bill of materials by scanning lib/<abi>/*.so files, smali package roots, and Maven metadata like pom.properties. For a fuller SBOM you can feed the results to OSV-Scanner or complement with MobSF and APKiD fingerprinting.

Does detecting a library mean the app is vulnerable?

No, presence does not equal vulnerable. You must confirm the exact shipped version falls within an advisory's affected range and that the app actually invokes the vulnerable code path with attacker-influenced data before citing a CVE.

Can this detect MavenGate or hijacked dependencies?

It surfaces the inventoried Maven group-ids so you can check whether a dependency's reverse-domain is abandoned or reclaimable, which is the MavenGate hijack indicator. Confirmation of a compromised artifact remains a manual research step.

What are the limitations of static dependency scanning?

Static inventory cannot prove reachability of a vulnerable code path or observe runtime PII exfiltration by tracker SDKs. Those require dynamic testing on an authorized device with Frida hooks and Burp or mitmproxy traffic inspection.