# Greptile — tools that shaped CodeVetter

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

A code review must follow a change beyond the diff.

## What we admire

Greptile’s repository graph puts distant functions, dependencies, and callers into the reviewer’s field of view. That is a useful corrective to reviews that judge a changed line without seeing the behavior around it.

## The principle that stayed

A finding becomes stronger when the reviewer can explain the path from the changed code to the affected behavior. Broad context should help generate a testable claim, rather than replace proof with confidence.

## Where CodeVetter stands

CodeVetter builds local structural and historical context for review, then asks for executable verification and a bounded evidence receipt. We have not established a head-to-head catch-rate advantage over Greptile; our benchmark limitations remain public.

## Sources

- [Greptile overview](https://www.greptile.com/docs/introduction) — the creator's own source
- [CodeVetter competitive landscape](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/competitive-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)