Free
$0 forever
Public repositories
Browser extension for any public PR. Structural diffs, unusual-edge signals, and AI review notes.
Code review for your architecture.
Not file diffs. Not text. Striff reviews every pull request as a dependency graph — boundary violations, coupling growth, and package cycles surfaced before merge.
What posts on your pull request — a diagram of what changed, plus ranked findings
apache/fineract PR #6063 Java 2 HIGH · 2 MEDIUM
Striff / architectural-review
Scroll to zoom · Drag to pan
Architecture diagram of this PR
The problem
Architecture matters more, not less.
Your team merges more AI-written code every week than anyone can read. Left unchecked, each merge piles on coupling and cycles until the architecture is unmaintainable. Striff catches that structural drift on every pull request.
Why it matters more in the AI era, not less — read the breakdown.
Research-backed — roots at ICCQ 2021
The proof, on live PRs
The riskiest changes look safe in a file diff.
These are real public pull requests. Each one looked routine file-by-file. Striff read the structure underneath — a new package cycle, a god-class forming, a migration quietly reversing — and posted the findings before merge.
- Live public PRs — open any of them and verify
- Findings posted on the PR before merge
- Zero overlap with AI reviewers' comments
7 findings posted on the live PR
5 crypto packages locked in a new cycle
0 visible in the file-by-file diff
Scroll to zoom · Drag to pan
Striff
reads the structure
220
components depend on the class this PR modifiesStable contract modified: SignatureAlgorithm
HIGH
New package cycle in crypto packages Dependency cycle:
crypto → crypto.signature → configuration → jwk → util → crypto. Package cycles break modularity and make future refactoring risky. HIGH
Stable contract modified — 44 dependents
Base64Util has afferent coupling of 44. WMC grew from 17 to 22, making this utility harder to test and maintain. MED
Test class with high efferent coupling
ECDSAPublicKeyTest is a new test with efferent coupling of 10. Tests this coupled to production internals tend to break with every refactor. AI reviewers on this PR caught implementation bugs — and zero of these findings. Striff reads the layer diff-based tools can't see. Use both.
More findings from major OSS repos → 5 findings posted on the live PR
6 components locked in a new package cycle
−10 WMC projected from the fix Striff prescribes
Scroll to zoom · Drag to pan
Striff
reads the structure
28 → 78
cyclomatic complexity (WMC) onPlacementInfo after this PR A god-class in the making — with a quantified fix
Efferent coupling jumped 6 → 15 alongside the WMC surge. Striff prescribes the remedy by name: extract aGroupingMetadataHandler and delegate — projected to cut EC by 1 and WMC by ~10. HIGH
New package cycle in DisplayManagement Cycle:
Zones → Descriptors.ShapeTablePlacementProvider → DisplayManagement → Descriptors → Shapes.ShapeDebugView → Shapes → Zones. The cycle spans 6 components this PR touches. HIGH
New directional boundary crossing New dependency from
OrchardCore.Tests.DisplayManagement.Decriptors to OrchardCore.DisplayManagement.Zones — no prior edge in this direction, and it skips 4 layers. MED
Complexity growth on GroupingMetadata
GroupingMetadata WMC grew by 27 (from 0 to 27) as a new component — consider extracting cohesive method groups. Striff doesn't just flag the god-class risk — it quantifies the fix: reduce EC by at least 1 and WMC by ~10 with a named extraction target.
More findings from major OSS repos → 2 structural findings on the live PR
4 components in the structural diff
0 visible in the file-by-file diff
Scroll to zoom · Drag to pan
Striff
reads the structure
0
releases of the new chart component — yet legacy already imports itMigration quietly reversing direction
ui-legacy.src.components.ui now imports from ui-react.src.components.ui.chart. The migration plan documents this component as "not yet shipped" — legacy reaching into the new package makes the migration harder to finish. MED
Premature cross-package import The new chart component isn't released yet, but
ui-legacy is already importing it. Worth confirming this is intentional and not a quiet step backward in the migration. AI reviewers on this PR caught implementation bugs — and zero of these findings. Striff reads the layer diff-based tools can't see. Use both.
More findings from major OSS repos →Built for engineering leaders
Fast teams. Architecture that holds.
Architectural drift is the tax your team pays later — slower PRs, harder onboarding, rewrites nobody budgeted for. Striff checks every PR against the architecture you've already documented, rolls it into an org-wide health dashboard, and never slows a single review down to do it.
HIGH
Package structure violation
DefaultCommandHandlerManager sits in implementation, but REFACTORING.md requires command handlers to live in handler. Doc-grounded — cites the file by name.
Last 6 monthsFebruary 2026 -- July 2026
Regressions flaggedA high-severity structural break Striff traced directly to this PR -- a new dependency cycle, a one-way boundary crossing, a stable component's contract shifting, or a sharp complexity jump. Deliberately rare: most PRs show zero.
30
Hotspots flaggedA lower-severity or anomaly-only finding worth a second look -- coupling or churn signals that don't rise to a confirmed structural regression. Usually zero or one per PR.
54
Clean PR rateShare of analyzed pull requests with zero regressions or hotspots flagged, over the last 6 months.
75%
High-risk PR rateShare of analyzed pull requests with at least one regression flagged, the more severe finding type, over the last 6 months.
7%
PRs analyzedTotal pull requests Striff reviewed for architecture across every active repo in this installation.
425
CoverageShare of GitHub PR-check webhook events (opened, updated, reopened) that completed analysis, over the last 6 months. Below 100% may mean PRs were skipped -- check billing status or repo connection.
93%
Flagged repos over timeEvery repo that has cracked the top-flagged list at any point in the last 6 months, tracked month by month. A repo can show a lower or zero count in months it wasn't flagged enough to be in that month's own top list -- more than one repo commonly appears here as the top spot reshuffles across months.
Recently flagged PRsThe 10 most recent pull requests this month with a structural regression or review hotspot -- click through to see exactly what was flagged.
Jul 2026
- acme-corp/core-api #4121 regression
Merge auth and billing request pipelines
- acme-corp/billing-service #4111 hotspot
Add retry backoff to invoice webhook consumer
- acme-corp/web-app #4101 hotspot
Refactor onboarding wizard step components
- acme-corp/core-api #4091 regression
Introduce direct DB call from the notifications module
- acme-corp/billing-service #4081 hotspot
Bump Stripe SDK to v18
- acme-corp/web-app #4071 hotspot
Extract shared form validation hook
- acme-corp/core-api #4061 regression
Collapse billing and shipping address models
- acme-corp/billing-service #4051 hotspot
Add idempotency key support to charge endpoint
- acme-corp/web-app #4041 hotspot
Move auth token refresh into shared context provider
- acme-corp/core-api #4031 regression
Route webhook fan-out through billing-service directly
Add token-bucket rate limiter to gateway middleware #1842
Conversation 12 Commits 6 Checks 4 Files changed 9
All checks have passed
4 successful checks
continuous-integration / build 44s Details
continuous-integration / test (312) 1m 12s Details
lint 18s Details
Striff — architecture
26s Details No boundary violations. Rate limiter stays inside gateway/middleware; matches ARCHITECTURE.md.
Free Chrome extension
See the architecture, right inside GitHub.
Install it and a new "Striffs" tab shows up next to Files changed on any public PR — no account, no backend to run.
Live architecture diagrams, right on the PR
A new "Striffs" tab appears next to GitHub's Files changed. Click it and get a real, pannable, zoomable dependency diagram of the change — not a static screenshot.
Click a component, drop a comment
Hover any class or package in the diagram, hit +, and post a real PR comment with a rendered sub-diagram attached — no screenshotting, no leaving the page.
AI notes overlaid directly on the graph
Architectural findings sit right on the diagram entities they describe, with inline thumbs up/down so your team can rate findings in place.
Zero setup, instant on any public repo
No backend to stand up, no account required to start. Install and go — repeat visits to the same PR load instantly from cache.
Get started
Start with public repos. Scale to your team.
Striff runs as a GitHub Check. No new tool to learn, no workflow to change. Start free on public repos, add private repos when you're ready.
Starter
$29 /mo · 5 repos
Private repos
GitHub App checks on every private PR. All detectors, GNN scoring, and automated review.
Enterprise
Talk to us
Self-hosted & 50+ repos
Private deployment, SSO, and audit workflows for organizations that need full control.
FAQ
Common questions
Does Striff replace CodeRabbit, Copilot, or Claude?
No — Striff complements them. AI reviewers catch code-level bugs, style violations, and logic errors. Striff catches architectural risks: dependency cycles, coupling spikes, boundary violations. Use them together for full coverage.
What languages does Striff support?
Java, TypeScript, Python, and C#. Go support is coming soon. Striff parses source code into a structural model using its own parser (Clarpse), not regex or text matching.
How does the AI work? Is it just an LLM wrapper?
No. Striff uses a neurosymbolic pipeline: deterministic structural analysis (8 detectors for cycles, coupling, boundaries, complexity) combined with a graph neural network trained on 129 well-architected codebases (AUC 0.91). The AI explains findings — it doesn't invent them. Every note is grounded in architectural facts.
Does it slow down my PR pipeline?
No. Striff runs as a GitHub Check, typically completing in under 30 seconds. It doesn't block merges unless configured to. The structural diff and review notes appear in the Checks tab.
What's the difference between the free extension and the GitHub App?
The browser extension is free and works on public repositories — you view structural diffs directly on GitHub PR pages. The GitHub App adds automated checks on every private PR, shared team workflow, and billing management. Plans start at $29/month.
Is my code sent to a third party?
Striff parses your code to extract structural information (components and relationships). Source code is processed in memory and not persisted. For enterprise needs, self-hosted deployment is available.
Architecture review for every pull request.
Striff works alongside your existing review tools. Install free for public repos — it runs on your next PR.