.NET codebase audit
For the CTO who inherited a codebase, the investor who is about to buy one, or the agency that has to quote on maintaining one. One week, fixed price, written for people who make decisions.
What you get
| Section | What it answers |
|---|---|
| Architecture | How the system is actually put together, versus how the diagram says. Dependency graph, boundaries, coupling hot spots. |
| Dependencies | Every package and runtime with version, support status and licence. What is out of support now and what will be within a year. |
| Security | Static analysis findings, secrets in source, authentication and input handling, ranked by exploitability. |
| Quality and tests | Test coverage where it matters, build reproducibility, the parts of the code that change most and are tested least. |
| Plan | A prioritised list with effort ranges: what to fix this month, this quarter, and what to leave alone. |
What it costs
From 1,500 EUR for a single solution up to roughly 150,000 lines, agreed up front after a look at the repository. Multi-repository systems are quoted the same way.
How the work is done
Remote, read-only access or a copy under NDA. Roslyn analyzers, dependency and churn analysis, and AI tooling do the reading at scale. I do the judgement: every finding in the report has been checked, and the plan reflects what a senior engineer would actually do first. Nothing from your code is used to train anything.