RichterMeasure the reach of a code change

Static impact analysis for Laravel. See the entry points a diff reaches, the ones no test references, and the hazards it carries, before the review starts.

Get started

Why Richter?

GitHub

Member-level impact

A one-method change seeds that method, not the whole class. Routes, controllers, jobs, listeners, policies, resources, Blade views, and Eloquent relations are all in the graph.

Honest degradation

A change the graph cannot place reads UNRESOLVED rather than "no impact". A coverage gap costs reach, and it still reports nothing as unaffected.

Test-coverage prompts

Every reached entry point is tagged as test-referenced or not. An entry point whose behaviour you changed with nothing referencing it is a place to add a test.

Blast radius on demand

Before a refactor, list a symbol's callers, its dependencies, and the entry surfaces behind them, or trace the shortest chain between two symbols.

Affected-test selection

Turn the diff's reach into a test selection, with an exit-code contract that fails toward running the full suite whenever it cannot be trusted.

Built for coding agents

A local MCP server exposes every analysis read-only, so an agent can work with the graph mid-review. The markdown report is ready to post as a PR comment.

What a report looks like

text

Entry points reached: 2
  - command::categories:sync  (app/Console/Commands/SyncCategories.php)  [test-referenced]
  - route::PATCH::/api/posts/{post}  (routes/api.php:41)  [⚠ no test references this]  [authed]

Findings (in the changed source itself):
  ! app/Models/Post.php: eager-load string 'ownerprofile': segment 'ownerprofile' is not a
    method on any model — check the relation name

Risk:   MEDIUM (advisory) — no hazard; 1 of 2 reached surfaces have no test referencing them
Impact: 2 entry point(s) · 7 impacted node(s)

Install it as a dev dependency and run one command on your branch. The analysis is static: it never executes your application's routes, jobs, or commands.

bash

composer require --dev sandermuller/richter
php artisan richter:detect-changes

Where to next

Step 1InstallationRequire the package, check the PHP and Laravel versions, and publish the config.Step 2Set up your projectTeach Richter your app's shape with an agent skill, or with two prompts you can paste anywhere.Step 3Detecting change impactRun the main command, read the report, and see how each entry point is reached.