anthropics/axt-verify Size, age and recent activity of the codebase. |
for people* (7/10)
for AI* (7/9)
Rule-of-thumb estimates
Rebuild value
Maintenance effort
analysis.maintainabilityScores.- Unit complexity4.9−1.216% of unit code with McCabe > 25
For people: Every branch is another path to understand and test; complex logic is where mistakes are made and missed in review.
For AI agents: Nested conditions are where generated changes break edge cases; complex units need more tests and review before an agent's change can be trusted.
- Unit size4.6−1.028% of unit code in units > 50 lines
For people: Long functions do many things at once: they are hard to name, read, test and reuse.
For AI agents: To change one line, an agent reads and often rewrites the whole function: bigger edits, more tokens, more breakage.
- File complexity5.0−0.625% of main code in files with McCabe sum > 125
For people: Complex files concentrate risk: understanding one means keeping many paths in mind.
For AI agents: Much to read and much logic to get right in one place: the costliest combination for an agent.
- File size5.8−0.325% of main code in files > 500 lines
For people: Large files are hard to navigate, mix responsibilities and attract merge conflicts.
For AI agents: Agents read whole files into their context: every change to a large file costs many tokens and crowds out other relevant code.
- Volume9.73,178 lines of main code
For people: More code is more to learn, search and keep in mind; onboarding and judging a change's impact slow down as it grows.
For AI agents: An agent sees only a slice at a time: the bigger the code base, the more it searches, and the likelier it misses relevant code or rewrites an existing helper.
- Duplication9.8<1% of main code duplicated
For people: A fix in one copy must be repeated in all the others; a missed copy becomes a bug.
For AI agents: Agents copy the patterns they find, so duplicates multiply; a change to one copy misses the others, and every copy costs context.
- Test code9.484 test lines per 100 main lines
For people: Tests document the intended behaviour and make changes safe.
For AI agents: Tests let an agent check its own work; without them its mistakes surface later, in review or in production.
- File size5.8−0.825% of main code in files > 500 lines
For AI agents: Agents read whole files into their context: every change to a large file costs many tokens and crowds out other relevant code.
For people: Large files are hard to navigate, mix responsibilities and attract merge conflicts.
- Unit size4.6−0.728% of unit code in units > 50 lines
For AI agents: To change one line, an agent reads and often rewrites the whole function: bigger edits, more tokens, more breakage.
For people: Long functions do many things at once: they are hard to name, read, test and reuse.
- Unit complexity4.9−0.616% of unit code with McCabe > 25
For AI agents: Nested conditions are where generated changes break edge cases; complex units need more tests and review before an agent's change can be trusted.
For people: Every branch is another path to understand and test; complex logic is where mistakes are made and missed in review.
- File complexity5.0−0.425% of main code in files with McCabe sum > 125
For AI agents: Much to read and much logic to get right in one place: the costliest combination for an agent.
For people: Complex files concentrate risk: understanding one means keeping many paths in mind.
- Test code9.4−0.184 test lines per 100 main lines
For AI agents: Tests let an agent check its own work; without them its mistakes surface later, in review or in production.
For people: Tests document the intended behaviour and make changes safe.
- Volume9.73,178 lines of main code
For AI agents: An agent sees only a slice at a time: the bigger the code base, the more it searches, and the likelier it misses relevant code or rewrites an existing helper.
For people: More code is more to learn, search and keep in mind; onboarding and judging a change's impact slow down as it grows.
- Duplication9.8<1% of main code duplicated
For AI agents: Agents copy the patterns they find, so duplicates multiply; a change to one copy misses the others, and every copy costs context.
For people: A fix in one copy must be repeated in all the others; a missed copy becomes a bug.
- 1McCabe 234791 LOC
- 2main.gocmd/axt-verify/McCabe 92351 LOC
- 3leaf.goleaf/McCabe 91356 LOC
- 4client.gocompliance/McCabe 78309 LOC
- 5events.gocmd/axt-verify/McCabe 75271 LOC
- 6checkpoint.gocheckpoint/McCabe 52199 LOC
- 7server.gointernal/testlog/McCabe 52256 LOC
- 8trust.gocmd/axt-verify/McCabe 30108 LOC
- 9testlog.gointernal/testlog/McCabe 30140 LOC
- 10McCabe 26123 LOC
| Standard analyses: | Main Code: 3,178 LOC (20 files) = GO (99%) + YAML (<1%) Secondary code: Test: 2,661 LOC (12); Generated: 0 LOC (0); Build & Deploy: 59 LOC (4); Other: 342 LOC (5); |
||
| Duplication: <1% | |||
| File Size: 0% long (>1000 LOC), 26% short (<= 200 LOC) | |||
|
|
Logical Component Decomposition: primary (7 components) | ||
| Goals: Keep the system simple and easy to change (4) | |||
| Experimental analyses (less reliable heuristic analyses): | |||
| Unit Size: 15% long (>100 LOC), 37% short (<= 10 LOC) | |||
| Conditional Complexity: 15% complex (McCabe index > 50), 34% simple (McCabe index <= 5) | |||
|
|
Static Component Dependencies: primary (7 components) | ||
No commit history found.
Visual Code Explorers
| MAIN (20) | Circles | Sunburst | |
| TEST (12) | Circles | Sunburst | |
| BUILD AND DEPLOYMENT (4) | Circles | Sunburst | |
| GENERATED (0) |
Circles
|
Sunburst
|
|
| OTHER (5) | Circles | Sunburst |
File Visualizations
File size views:
Duplication views:
File age views:
File change frequency views:
Contributors per file views:
Contributor Visualizations
Contributor dependency views:
Components and Dependencies Visualizations
| Components | Temporal Dependencies | Duplication | Commits Racing Charts | ||||||||||
| 30 days | 3 months | 6 months | |||||||||||
| PRIMARY (7) | Bubble Chart | Tree Map |
2D
|
3D
|
2D
|
3D
|
2D
|
3D
|
All Time | 12 Months | |||
File Dependencies Visualizations
Temporal dependencies among files:
|
Units Visualizations
Unit size and conditional complexity views:
Lists of Files Per Scope
- MAIN (20 files)
- TEST (12 files)
- BUILD AND DEPLOYMENT (4 files)
-
GENERATED
- OTHER (5 files)
- FILES: History Data
- IGNORED FILES: By Extension | By Rule
Analysis Results
- CONFIGURATION: JSON
- ALL ANALYSIS RESULTS: JSON
- DUPLICATES: TXT | JSON
- UNITS: TXT | JSON
- CONTRIBUTORS: TXT | JSON
- LOGICAL DECOMPOSITIONS: JSON
- CONCERNS: JSON
- CONTROLS: TXT
- ALL METRICS: TXT