See what a change affects
Product previewThe callers, consumers and state a change reaches, and where the analysis can’t establish a relationship.
Code review with evidence
Built to reveal change impact, catch unhealthy drift, and check your project’s rules—whether people or agents write the code.
Every finding links to its source and states its assumptions and limits.
Report and source content is shown in its original language; interface labels are translated.
Why now
Intent is spread across code, tests, documentation and agent instructions. Wofanu is built to connect those expectations with the changes being reviewed.
What Wofanu is built to do
Wofanu is built to read each change together with the code it reaches and the rules your project declares, whoever wrote it.
The callers, consumers and state a change reaches, and where the analysis can’t establish a relationship.
What each change introduces, improves or makes harder to follow, compared with your main branch, review after review.
Ownership and boundary rules checked against the evidence. A rule is reported as broken only when the evidence establishes it.
Write your rules once, where your coding agents read them. Each change is checked against them, whoever wrote it, and instructions that point at code that no longer exists are flagged.
Example of a customer-declared rule
Only the billing component may change an invoice’s payment status.
You don’t need rules to start. A repository review works without them.
How a review reports against it
A finding needs an applicable rule and adequate evidence. Missing evidence is not a violation.
In your merge requests
An illustrative comment on one changed function: what improved, what became harder to follow, what it reaches, and which questions stay open.
Product preview · illustrativeReport and source content is shown in its original language; interface labels are translated.
acme / billing / Merge requests / !482
Round invoice totals to the currency’s minor unit
Open line-rounding into main
Compared with main, this change to invoice.total:
Money branch, the total now rounds through Money.round.billing/invoice.py:93totals.legacy with hook("total"). Which handlers run: not established.billing/invoice.py:94api.invoices.show, and export.csv_row as a candidate: doc.total() may also be CreditNote.total.api/invoices.py:120 · export/csv.py:41test_invoice_total refers to invoice.total. No referring test was identified for the hook("total") path in the analysed files under tests/ at 4f2a91c.tests/test_invoice.py:12Not analysed: tests/generated/, created at build time.Rules from AGENTS.md
Money.round · line 12Money branch.Hook fallback: not established.On main, this was a rule violation. Assumes amount: Money (line 90).billing/ never calls api/ · line 15hook("total") could be anywhere.It held on main.Stale instruction: AGENTS.md line 21 names billing/rounding.py, which was removed in !471. Agents following it may look in the wrong place.
Static analysis of 4f2a91c against main, without running your application. Findings are advisory. Open the full report
In a merge request. The host interface is simplified and the report is illustrative.
A real analysis
A historical TinyDB case, shown the way a Wofanu report presents it.
This case was reported and fixed upstream before we analysed it, and it was used while developing and checking the analysis. It shows what a finding contains. It is not a measure of how often the analysis finds problems.
Open the full reportReport and source content is shown in its original language; interface labels are translated.
tinydb/table.py · Table.insert_multiple
In the studied mixed insertion batch, the later write can replace the earlier document.
Static analysis
Establishedunder these assumptions
With an empty table and no cached ID, the new ID is read from stored data before the batch commits, so it can equal the explicit ID.
Not established
Whether any real caller passes a batch like this.
Runtime check · run separately
Next check
Inspect the ID allocator and run a mixed-batch regression test.
Reading a finding
Reports answer three separate questions, each with its own labels.
Whether the analysis supports a relation, needs it confirmed, couldn’t settle it, or shows that it doesn’t hold.
Code that wasn’t examined is listed with the reason. Nothing is concluded about it.
A rule violation needs a rule you declared and adequate evidence. A known fix is a historical case already fixed upstream.
How it works
Wofanu is built to follow your main branch and its merge requests.
Product previewEstablish the supported source and the relationships available for inspection. Record analysis gaps.
Each change is compared with the baseline and checked against your rules.
Product previewEach finding arrives with its evidence, in a report you can inspect.
In your merge requests, too. Product preview
Questions
No. It analyses source code without running it. When a report includes a runtime check, the check is run separately and labelled that way.
No. Wofanu supplies evidence for those decisions. Static analysis does not establish every runtime behavior or prove that a change is safe.
Some findings are bugs. Others are broken rules or questions that still need checking. Each finding says what it rests on.
No. The analysis reads the code, whoever wrote it.
No. A repository review works without them. Add rules when you want reviews to check your intent.
Wofanu starts with Python. See current availability
Data handling describes how access, processing, retention and deletion work. Data handling draft
Tell us about your repository and what you want to understand.
Or write to hello@wofanu.com
Please don’t send source archives, credentials or access tokens. This inquiry does not start analysis.
Current availability