# Arbor — tools that shaped CodeVetter

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

Deterministic graph traversal is a useful answer to structural questions.

## What we admire

Arbor’s graph-native approach values exact symbol relationships over a vague semantic match. That is a principled way to answer questions such as “what calls this function?” and “what might this change affect?”

## The principle that stayed

A graph edge should carry a source location and a defined extraction rule. Determinism makes a result repeatable, although a parser graph still cannot prove the program’s runtime behavior.

## Where CodeVetter stands

CodeVetter owns a bundled Tree-sitter structural graph and marks extracted links as evidence leads. Arbor’s philosophy informed our evaluation, but its engine is not bundled.

## Sources

- [Arbor source repository](https://github.com/getArbor-dev/arbor) — the creator's own source
- [CodeVetter codebase-context research](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/codebase-context-tools-landscape.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)