Static analysis for C# — locally, in 60 seconds.
Scan your C# / .NET project for complexity outliers, oversized methods,
parameter-heavy signatures, deeply-nested logic, and semantically-duplicate
helpers — with the ik CLI. The structural metrics run
fully in-process via the
chamele library, so
there's no Roslyn analyzer or MSBuild step to wire up. Pairs cleanly with
whatever dotnet format / Roslyn analyzer setup you already
have.
Running on an ASP.NET Core API
What we check, and how.
C# language-specific dependency audit (NuGet), dead-code, error-handling, magic-number, import-graph, and test-framework detectors aren't wired up yet — the structural-metric and duplication checks above are the C# story for now. Track progress on the blog or email us if NuGet CVE scanning matters for your repo.
The smells nobody refactors out.
A single OrdersController action that validates, maps, persists, and emails in 300 lines. Function-length and complexity flag it as one finding each so the refactor target is obvious.
Methods that grew one argument at a time until they take nine. AI keeps appending parameters rather than introducing a request object; parameter-count surfaces every offender.
if / try pyramidsDeeply-nested guard clauses and try/catch ladders that bury the happy path five levels deep. Nesting-depth points at the exact methods worth flattening with early returns.
The same mapping or validation logic regenerated in three projects with different names. jscpd finds the token-level copies; the embedded-LLM semdup check catches the ones reworded just enough to slip past it.
Run it on your C# project.
Install in one line, scan in under a minute. No account required. The C# structural checks need no extra tooling — chamele is linked into ik.
Scan another language
Cross-cutting checks: secret scanning · dependency vulnerability scanning · AI code review