---
type: "post"
id: "openqodex-0-15-0-adds-java-support-to-dbf796"
slug: "openqodex-0-15-0-adds-java-support-to-dbf796"
title: "OpenQodex 0.15.0 adds Java support to its code graph"
description: "OpenQodex 0.15.0 adds Java parsing to its code graph without requiring a build step."
retrieval_nugget: "OpenQodex 0.15.0 adds Java parsing to its code graph without requiring a build step. The release says the graph resolves possible implementations behind interface or base-class calls and distinguishes overloads by argument count, while Java reviews identify callers and their tiers. This gives teams a new way to inspect change impact, but the release provides no accuracy or performance measurements."
published_at: "2026-11-08"
updated_at: "2026-11-08"
record_date: "2026-11-08"
date_kind: "published_at"
topics: ["coding-agents","developer-tools"]
entities: ["OpenQodex","Martian","Greptile"]
related_patterns: []
novelty_label: "new_fact"
what_changed: null
prior_refs: []
source_url: "https://github.com/openqodex/openqodex/releases/tag/openqodex@0.15.0"
source_urls: ["https://github.com/openqodex/openqodex/releases/tag/openqodex@0.15.0"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:openqodex-0-15-0-adds-java-support-to-dbf796"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/openqodex-0-15-0-adds-java-support-to-dbf796/","markdown":"https://newruntime.com/posts/openqodex-0-15-0-adds-java-support-to-dbf796.md","json":"https://newruntime.com/posts/openqodex-0-15-0-adds-java-support-to-dbf796.json"}
markdown_url: "https://newruntime.com/posts/openqodex-0-15-0-adds-java-support-to-dbf796.md"
---

# OpenQodex 0.15.0 adds Java support to its code graph

## Retrieval answer

OpenQodex 0.15.0 adds Java parsing to its code graph without requiring a build step. The release says the graph resolves possible implementations behind interface or base-class calls and distinguishes overloads by argument count, while Java reviews identify callers and their tiers. This gives teams a new way to inspect change impact, but the release provides no accuracy or performance measurements.

## Summary
OpenQodex 0.15.0 adds Java parsing to its code graph without requiring a build step. The release says the graph resolves possible implementations behind interface or base-class calls and distinguishes overloads by argument count, while Java reviews identify callers and their tiers. This gives teams a new way to inspect change impact, but the release provides no accuracy or performance measurements.

## What happened
OpenQodex’s GitHub release for version 0.15.0, published on October 26, lists Java support for the code graph as its main minor change. The release says the graph reads Java types, methods, constructors, imports, static imports and calls, with no build step. It does not describe the supported Java versions, repository-size limits or any setup requirements beyond that statement.

The release describes two details about how the graph represents calls. When a call passes through an interface or a base class, the graph lists implementations that may run. It also tells overloaded methods apart by their argument count. These capabilities are relevant to tracing effects across a codebase: a caller may depend on a method indirectly, and a method name alone may not identify which overload is in play. The release does not explain how it handles cases where argument count is insufficient to distinguish overloads, or how it represents uncertainty among possible implementations.

For reviews of Java changes, OpenQodex says the review names the change’s callers and gives each caller a tier. The release does not define those tiers or say how the review selects, ranks or validates callers. It also does not report a test set, benchmark result, comparison with another code-analysis tool, or a measured reduction in missed dependencies. The announcement therefore establishes the feature’s stated behavior, not its reliability on a particular project.

The same release includes a patch to benchmark documentation. It says the comparison record attaches judged runs with their board evidence, that scores read Martian and Greptile board results, and that calibration takes a comment form. These are changes to benchmark-record documentation and workflow; the release does not announce new benchmark scores. GitHub lists 66 commits to main since this release, but that count alone does not describe what subsequent changes contain.

## What the archive adds
New Runtime’s earlier coverage on October 19 described OpenQodex as combining scanner output with a separate AI review pass before a push ([OpenQodex: An open source AI code reviewer](https://newruntime.com/posts/openqodex-an-open-source-ai-code-reviewer-analysis-88bbb2/)). Version 0.15.0 is a new fact on that known story: it extends the code graph and Java review context, rather than announcing a new product.

## Trend signal
This does not yet fit a pattern New Runtime tracks. Caller and tier information could help reviewers focus attention when evaluating a change, but the release does not measure whether it reduces review time or improves defect detection.

## Why now
The release gives no explanation for the timing of Java support or the benchmark-documentation changes. Its publication establishes when the changes shipped, but not what prompted them.

## Why it matters
A code graph that can identify indirect Java callers and possible implementations can make a review more informative than a diff alone, especially when a change affects an interface or a base class. Showing callers with tiers may also help a team decide where human attention is most valuable. The practical question is whether the graph is sufficiently complete and precise on the team’s actual codebase: an incomplete caller map can create false confidence, while a noisy one can add review burden.

Teams evaluating the release should test it against representative Java changes, including overloaded methods and interface dispatch, then compare its caller list with their own dependency knowledge. The release’s benchmark-record changes may make judged runs easier to inspect, but they do not themselves validate the Java graph. Treat this as added review context to verify, not evidence that review quality or speed has already improved.

## Limits and uncertainty
The release does not identify supported Java versions, tested project sizes, performance costs or parsing limitations. It does not define caller tiers, report accuracy for implementation resolution, or provide an independent evaluation of Java review results. It is also unclear how the graph handles dynamic dispatch edge cases, generated code or dependencies that require build configuration. The benchmark-documentation changes are described, but no new scores or underlying judged-run results are included in the release notes.

## Skill to build now
Choose a recent Java change in your repository that modifies an interface, base class or overloaded method. Run OpenQodex 0.15.0 against it and compare the graph’s possible implementations and named callers with a manually checked set. Record false positives and omissions, and verify what the caller tiers mean before using them to prioritize review. This turns the new capability into a local fit check rather than assuming the release’s description guarantees coverage.

## Reader takeaway
OpenQodex 0.15.0 adds a potentially useful Java change-impact view: code graphing without a build step, possible targets for indirect calls and callers listed in reviews. The release establishes those features, but not their accuracy or review-time benefits. Validate the graph on real Java changes before relying on it to guide human review.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Developer Tools](https://newruntime.com/topics/developer-tools.md): Explore the developer-tools topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)