Technical audit of a large .NET codebase
Solo technical audit of a large legacy .NET platform (38 production sites, around 140k lines of code): 84 prioritized findings across security, performance and architecture, delivered as a costed modernization roadmap.
Audit
.NET
Security
Architecture
Context. A standalone technical audit of a large legacy .NET 8 web platform: 38 production sites plus a multi-tenant back-office, around 140k lines of C#, and about 15 third-party integrations. I read the whole codebase and wrote the report as the Capcod architect on the job.
#What I delivered
- 84 findings across security, performance, architecture and quality. Each one is scored by criticality, risk and effort to give a clear P1 to P4 priority, and traced to the exact file and line with the offending code.
- A 4-phase modernization roadmap, costed in person-days, with a security-first phase that has to come before anything else.
- A client-facing report (Word, PDF and a slide deck) plus a modernization plan.
#Why it matters
This is the flip side of building. It shows I can read a large, unfamiliar codebase, judge it from several angles, prioritize hard, and hand a client a plan they can act on.
#Stack
.NET 8 / ASP.NET Core, EF Core, SQL Server (multi-tenant), architecture and security review, CAPCOD audit methodology and report generation.