Codebase Audit
Audit an existing codebase or system and produce an evidence-backed findings register and prioritized remediation roadmap.
Sample result
How it works
What Codebase Audit does
Covers scoping the audit questions, a read-only orientation, eight dimensions (architecture, maintainability, reliability, security, performance, test coverage, operability, delivery), change-frequency by complexity hotspots, test-gap mapping to critical paths, findings with evidence and confidence, severity times likelihood times exposure scoring, and now/next/later sequencing.
Use it when
Someone asks to audit a codebase, assess technical debt, review the health of an inherited or acquired system, find reliability or security gaps, judge whether to rewrite or refactor, or prepare due diligence on a code base.
Use something else for
Dependency version and licence health alone, for planning a data or platform move, for designing the target system, or for reviewing a single change.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Audit report, findings register, hotspot analysis and remediation roadmap
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Codebase Audit
Updated Oct 20, 2026.
What does Codebase Audit do?
Audit an existing codebase or system and produce an evidence-backed findings register and prioritized remediation roadmap. Covers scoping the audit questions, a read-only orientation, eight dimensions (architecture, maintainability, reliability, security, performance, test coverage, operability, delivery), change-frequency by complexity hotspots, test-gap mapping to critical paths, findings with evidence and confidence, severity times likelihood times exposure scoring, and now/next/later sequencing. Use when someone asks to audit a codebase, assess technical debt, review the health of an inherited or acquired system, find reliability or security gaps, judge whether to rewrite or refactor, or prepare due diligence on a code base. Do not use for dependency version and licence health alone (use dependency-health), for planning a data or platform move (use migration-plan), for designing the target system (use technical-architecture), or for reviewing a single change (use gitnexus-review).
Who is Codebase Audit for?
It is designed for engineering leads, CTOs, technical due-diligence reviewers, new maintainers of inherited systems and product owners.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Codebase Audit produce?
Audit report, findings register, hotspot analysis and remediation roadmap. Results come back with their sources and any open questions for you to check before anything is used.
How much does Codebase Audit cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt74jt002i…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Codebase Audit fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.