# GitNexus — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/gitnexus

A code graph can be exposed as a useful interface for agents.

## What we admire

GitNexus explores code knowledge graphs that an agent can query for relationships and flows. It was a useful comparison while we decided how much of our graph should be an owned local engine.

## The principle that stayed

The graph’s runtime and parser versions affect reproducibility. An optional external adapter can be useful, but the canonical evidence path should remain available offline.

## Where CodeVetter stands

The graph decision keeps CodeVetter’s Tree-sitter index in Rust and treats a GitNexus subprocess as optional secondary research. It is not required by the product.

## Sources

- [GitNexus source repository](https://github.com/abhigyanpatwari/GitNexus) — the creator's own source
- [CodeVetter OSS integration decision](https://github.com/Codevetter/codevetter/blob/main/docs/architecture/decisions/oss-integration.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)