The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A five-minute English walkthrough of my public ASP.NET Core audit case.
Inside:
• N+1 in EF Core — evidence, impact and a server-side fix
• P0 security findings: tracked secrets and an unprotected admin endpoint
• DbContext lifetime and background-worker reliability
• a P0/P1/P2 remediation backlog
• a focused PR with five fixes and passing CI
• repository readiness for Codex and other coding agents
The walkthrough is fully in English and uses a dedicated technical narration script for clear pronunciation of .NET, ASP.NET Core, EF Core, DbContext, SQL, HTTP and Docker.
Pilot audit: one .NET service, three business days, launch price €199 / 20,000 ₽.
Public case: https://github.com/Dalkory/DotnetAuditDemo
Contact: taushkanovdaniil@gmail.com · Telegram @DanilDotNet
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
One ASP.NET Core endpoint can hide dozens of database round trips.
In my public .NET audit demo, an orders endpoint loaded a list and then queried the customer table inside a loop. That creates an N+1 query pattern: 1 order query + N customer queries.
Risk: latency and database load grow with every item returned.
Remediation:
• server-side projection
• AsNoTracking for read-only work
• bounded pagination
• query-count validation in tests
The focused remediation PR also fixes four other priority findings: DbContext lifetime, unauthenticated admin access, committed secrets, and unbounded materialization.
Demo report and code: https://github.com/Dalkory/DotnetAuditDemo
I provide fixed-scope, asynchronous .NET Backend & AI Readiness Audits with a written report, prioritized backlog, effort estimates, and recorded walkthrough.
asp.net
ASP.NET Core | Open-source web framework for .NET
Build web apps and services that run on Windows, Linux, and macOS using C#, HTML, CSS, and JavaScript. Get started for free on Windows, Linux, or macOS.
Dotnet Audit Studio is accepting the first three pilot projects for a fixed-scope .NET Backend & AI Readiness Audit.
Best fit:
• an existing C# backend that became hard to change
• slow EF Core or SQL paths
• reliability issues around DI, async code, HTTP clients, or background workers
• weak tests or CI/CD gates
• a repository that needs clearer boundaries before introducing coding agents
You receive:
Executive summary
Architecture map
5–7 prioritized findings
Concrete recommendations and effort estimates
Remediation backlog
Recorded walkthrough
Launch package: $199, one service/repository, three business days, no code changes included.
The process is asynchronous and fixed-scope. Production infrastructure and penetration testing are not included. Private code is not sent to third-party AI services without explicit permission.
Public sample report: https://github.com/Dalkory/DotnetAuditDemo/blob/main/AUDIT_REPORT.md
Contact: taushkanovdaniil@gmail.com | Telegram @DanilDotNet
github.com
DotnetAuditDemo/AUDIT_REPORT.md at main · Dalkory/DotnetAuditDemo
ASP.NET Core backend audit case study: 15 findings, prioritized remediation plan, and a before/after PR. - Dalkory/DotnetAuditDemo
The most dangerous SaaS bugs are often inconsistencies, not complete failures.
A product can appear to work while different parts of the system tell different stories.
For example:
• the dashboard shows a booking as confirmed
• the calendar still shows it as pending
• the client receives a reminder
• the API returns a different status
• mobile allows an action that desktop blocks
Each screen may look reasonable on its own.
Together, they create a product users cannot trust.
This usually happens when several parts of the system interpret the same data independently.
One page reads a raw status.
Another calculates its own version.
A mobile flow still uses older logic.
A notification is sent before the latest state is checked.
The result is not one obvious bug.
It is several slightly different versions of the truth.
When I audit a SaaS workflow, I check whether the full system behaves consistently:
• where the source of truth lives
• whether all screens use the same state definition
• whether desktop and mobile allow the same actions
• whether notifications reflect the latest data
• whether one workflow can change state without other surfaces updating
• whether booking, payment, confirmation and delivery remain separate facts
This matters especially in booking systems, CRMs, dashboards and subscription products.
A small inconsistency can lead to duplicate actions, incorrect access, misleading payment states, missed appointments and unnecessary support work.
The safest fix is often not another frontend condition.
It is defining one clear contract and making every surface use it consistently.
That is one of the main things I look for when auditing early-stage SaaS products:
not only whether each feature works, but whether the whole product agrees on what is true.
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?