Your app, drawn from the code. And what is wrong with it.
GitGraf reads the repository through a read-only GitHub App and draws it: features, the code behind them, and the services they lean on. Every problem it finds is one row per cause, with the task that fixes it.
AI made coding faster. Knowing what is wrong got harder.
Nobody has read the whole repository lately, and the things wrong with it are spread across advisories, migrations, config files, and dashboards.
Nothing shows the whole app.
Which features exist, which code serves them, and which services they lean on lives in somebody’s head.
Scanners return symptoms.
One mistake made 137 times comes back as 137 rows, so the list gets closed rather than worked through.
An alert is not a task.
An agent needs the file, the change, the constraints, and a check that says whether the fix held.
See the whole app. Know what is wrong with it.
One board: the map of features, code, and services, the findings that touch each node, and every open branch with the station it is waiting at.
Illustrative Product Preview
Branches
Live
Illustrative branch board: the seven stations a branch passes, Pushed, CI, Preview, Database, QA, Review, and Merged, with this branch waiting on review.⑂
PushedGitHub has the commit● Pushed
CI
CIReports, never blocks● Reported
PV
PreviewMatched to the commit● Ready
DB
DatabaseNo migration due● In sync
QA
QADesktop, tablet, mobile● Passed
R
ReviewWaiting on a person● Needs You
Merge Readiness
Review
Merging happens on GitHub
Stations Clear
5 of 7
Findings Here
2 confirmed
Check Re-run
Passed
Next Action
Review
Findings
One row per cause, not per symptom.
A database with 137 functions missing a pinned search_path is one finding with 137 instances, one task, and one check. A finding is confirmed when GitGraf can point at the thing itself, and suspected when it can only say what would settle it.
Task PacketProblem, where, change, constraints, done when
For an agent
✓
VerificationThe finding’s own check, re-run at your commit
GitGraf
The versions that will actually run.
GitGraf reads the lockfile rather than package.json, asks the registry what has been published since, and checks what is installed against the OSV advisory database. Agents read the same answer through gitgraf_stack.
GitGraf dependency map: Node 22.9, React 19.0, PostgreSQL 16.4, Redis 7.4, Python 3.12 and TypeScript 5.6 orbiting the GitGraf mark, with the installed version shown under each.
Lockfile Versions
Read
Latest Published
Checked
Known Advisories
OSV
Agent Access
MCP
GitHub remembers the commits. GitGraf remembers what each branch is waiting on.
Seven stations, from webhooks and cloud runners. CI reports and never blocks, so a red check holds no station, and when GitHub refuses to run the jobs over a spending limit the board says CI did not run rather than failed, because nothing in the branch is wrong.
The seven stations a branch passes, and where each fact comes from
Type
Stage
Context
Status
Source
⑂
Pushed
GitHub has this commit
● Pushed
Webhook
⑂
CI
Checks reported, holding nothing
● Reported
Checks API
⑂
Preview
Deployment matched to the commit
● Ready
Vercel
⑂
Database
No migration on this branch is due
● In sync
Supabase
⑂
QA
Browser checks against the preview
● Passed
GitGraf
⑂
Review
Somebody still has to look
● Needs You
GitHub
⑂
Merged
Merging happens on GitHub
● Not merged
GitHub
GitGraf Cloud QA
Nothing here marks its own work as passed.
Cloud workers open the preview built for that commit at three viewports and report what happened. A branch carrying a migration that has not been applied holds the QA station instead of collecting three green ticks it has not earned.
Set it up in the browser. Nothing runs on your machine.
Install the read-only GitHub App on the repository you choose, and the first scan starts by itself. Connect Vercel or Supabase afterwards if you want previews, migrations, and QA on the board.
Read only, by permission.The App has no contents:write, so GitGraf cannot push, cannot merge, and cannot change a file. A finding quotes the line that matched, never the value of a secret.
GitHub
Install the Read-only App
Choose the account and which repositories GitGraf may read. Nothing it is granted can write.
Repository
Choose a Repository
It becomes a project, and the first scan draws the map and lists what it finds wrong.
Agents
Point Your Agent at the URL
One hosted MCP server and one project token, pasted into Claude Code, Codex, Cursor, or anything else that speaks MCP.
Point it at a repository. Read what it says.
Join the GitGraf early-access programme for the app map, the findings and their tasks, the branch board, stack health, and one hosted MCP for every agent.
