codeanalyzer-java
One JAR turns an enterprise Java project into a symbol table and call graph — emitted as a single versioned JSON schema your tools can consume.
Point codeanalyzer-java at a Java project and get back analysis.json — a single document describing every class, method, field, and import in the codebase, plus an interprocedural call graph computed by WALA. The schema is the same shape the CLDK Python SDK deserializes into typed models, so whatever consumes it — an agent, a script, or the SDK — works against structured analysis instead of raw source.
Start here
Section titled “Start here” What is codeanalyzer-java? The mental model: project → JAR → analysis.json → typed consumers.
Quickstart Build the JAR and run your first analysis in a couple of minutes.
Installation Run as a fat JAR, or compile a native binary with GraalVM.
Architecture The pipeline: Javaparser symbol extraction + WALA call-graph construction.
Go deeper
Section titled “Go deeper” CLI reference Every flag: input, analysis level, build command, target files.
Output schema The full shape of analysis.json — symbol table and call graph.
Analysis levels Level 1 (symbol table) vs. level 2 (+ call graph), and what each costs.
Python SDK integration How CLDK shells out to this JAR and wraps the output as JavaAnalysis.