Devotd Github
NewDeveloper tools

openqodex/openqodex v0.14.0 — staged review and audit changes

openqodex/openqodex v0.14.0 is a release that changed the review procedure along with the lockfile and graph index features, and updated the package version.

Repositoryopenqodex/openqodex ↗

openqodex/openqodex v0.14.0 is a release that changed the review procedure along with the lockfile and graph index features, and updated the package version.

GitHub description: Open source code review that runs in your coding agent before you push. Scanners plus a separate AI reviewer, on your own login, no key.

stars
★ 808
Forks
67
Language
TypeScript
License
Apache-2.0
Latest release
openqodex@0.14.0
Read original source ↗View on GitHub ↗

openqodex/openqodex is an open-source code review tool that runs in a coding agent before a push. The 2026-10-23 commit 68ef6b8 reflects the openqodex v0.14.0 release version. The README, GitHub Action, pre-commit configuration, agent instructions, and plugin manifest were changed to point to the new version. The commit message announces the package version update, and a CLI changelog was also added.

This release's changelog contains a feature that breaks the review into stages. Two finder sessions examine the changed files and the surrounding code, and a verifier session checks the discovered candidates so that only confirmed items remain as findings. Items related to style, naming, documentation, and tests are marked as observations, distinguished from findings and the final verdict. It is also possible to turn off the staged review through configuration and run in a single pass. Changes were also recorded to check the repository's lockfile during review and scanning, and to show recommendations outside the scanner together with the fixable versions.

The library changelog describes the public API for graph queries and index files. It supports the flow of saving a graph to a file, reading it back, and querying it, and the file returned by `writeIndex` includes `projects.json`. This commit centers on the release merge and the version update, and the feature description is based on changeset records that were removed during the merge process. Therefore, the performance or accuracy of the feature cannot be evaluated from this material alone.