dependency-decompile

Recover readable source code for critical-path dependencies lacking source.

83|8|Updated May 6, 2026
One-click install
npx skills add https://github.com/Q16G/aster --skill dependency-decompile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-decompile
Source: https://github.com/Q16G/aster/tree/main/skills/code-audit/dependency-decompile
Command: npx skills add https://github.com/Q16G/aster --skill dependency-decompile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill recovers readable source code for dependencies that lack source on critical paths during security audits, enabling more accurate analysis of attacks and data flows.

Core Features & Use Cases

  • Recover readable source either from official sources when available or via decompilation for critical-path dependencies lacking source.
  • Document provenance and uncertainty to support audit trails and compliance.
  • Use case: during SCA triage, when a jar/war has no sources, recover source to analyze potential vulnerabilities and verify behavior.

Quick Start

Decompile a no-source dependency on a critical path to recover readable source and document its provenance.

Frequently Asked Questions about dependency-decompile

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

FAQPage Schema
How do I recover source code for dependencies lacking source during a security audit?

Decompiling dependencies on critical paths is necessary when source is unavailable and the security decision lies inside the dependency. You need it for accurate SCA triage, entry-point analysis, and data-flow tracing to verify potential vulnerabilities and behavior.

When do I need to decompile dependencies for SCA triage?

Decompiling dependencies on critical paths is necessary when source is unavailable and the security decision lies inside the dependency. You need it for accurate SCA triage, entry-point analysis, and data-flow tracing to verify potential vulnerabilities and behavior.

How to decide whether decompilation is warranted for a no-source jar or war?

Decompilation is warranted based on path importance and whether the security decision lies inside the dependency. The Skill applies offline triage logic to assess public vs private libraries and local sources before deciding to decompile no-source jars or wars.

Does this approach work for data-flow tracing in reverse engineering?

Yes, it works for data-flow tracing in reverse engineering by recovering readable source from key-path dependencies. This enables accurate tracking of attacks and data flows when dependencies lack source, documenting provenance to support audit trails.

What are the limitations of decompiling dependencies for source recovery?

Limitations include uncertainty in recovered source and the need to assess whether decompilation is warranted. The Skill mitigates this by applying offline triage logic to evaluate public vs private libraries and annotating provenance and uncertainty for audit trails.