Evincia
We point Modernization Shield at well-known open-source .NET codebases -- in the open. The same engine, the same twelve risk categories, check-it-yourself provenance. Including, when it happens, the places our own engine got it wrong.
Evincia does not publish client logos. The substitute is stronger: we run the exact diagnostic a client receives against codebases anyone can read, and we publish the readiness profile -- findings, score, and what would break first -- with the commit you can check it against.
A teardown is not a verdict on the people who built the code. Open-source maintainers ship under constraints a risk report knows nothing about. A teardown reads a codebase the way a modernization team has to: where the platform risk concentrates, what carries the migration, and what an estimate would have to absorb before the budget is set.
Before any of this was published, the engine was run across a broad corpus of public .NET projects -- to prove it is deterministic (same code in, same findings out), to check that the scored profiles built on its findings separate the eras -- the legacy cohort lands in Red at 18 to 44; the modern control application lands at 77, a full band above it and, scored honestly, three points short of Green -- and to find its own blind spots. The breadth is the calibration.
The corpus spans names a .NET engineer will recognize -- ORMs, loggers, schedulers, CMS platforms, e-commerce monoliths, an IDE. Recognizable code.
Running the diagnostic across dozens of real codebases surfaced real false positives: a version string read as a hardcoded address, a single-project app whose service seam the heuristic missed, a modern library scored on a legacy axis because it multi-targets an old framework for compatibility. We caught them, wrote them down, and fixed the engine. Every profile flags any finding a later corrected run would change.
A diagnostic you can trust is one that tells you where it was wrong before you have to find out. That is the entire point of calibrating in public.
A single-project ASP.NET Web Forms storefront on .NET Framework 4.7.2 -- the deliberately-legacy reference app from Microsoft's eShopModernizing sample. Platform-bound and certain: the dominant risk is the platform itself, and what breaks first is the web layer the moment System.Web is removed.
A 31-project, multi-tenant .NET Framework content-management platform on net40 -- eight swappable storage backends and three template engines at once. The deepest calibration subject so far: total platform lock-in, an internal WCF file server and Windows COM interop, and no test safety net at all.
A 7-project ASP.NET MVC 5 + EF6 reference app on .NET Framework 4.5 -- a Marlabs DDD teaching sample with a real test project and clean layering. The mildest Red of the legacy cohort: total net45 lock-in and a System.Web rewrite, but a genuinely better starting position than its peers.
Microsoft's clean-architecture ASP.NET Core reference app -- ten projects, all on .NET 8, the modern sibling of the legacy eShop profile above. The control pair for the whole program: zero platform-obsolescence findings, work that is hygiene rather than rewrites -- and a score of 77, three points short of Green, because the judgment layer does not hand out free Greens. A gauge that only ever reads Red is not a gauge; neither is one that reads Green on cue.
Additional teardowns are drafted and in senior architect review -- a 99-project IDE among them, and others across the corpus. Each is held until its confirming engine re-run and naming review are complete. They publish here as they clear.
The public teardowns run the diagnostic on code anyone can inspect. The SocialGoal sample Modernization Risk Report shows how the same kind of evidence is organized into a decision-ready report for leadership.
Public Codebase Teardowns apply the Modernization Shield diagnostic to open-source .NET projects under permissive licenses, paraphrased and attributed, with check-it-yourself provenance. They are illustrative readiness profiles, not engagements, and not a judgment of the projects' maintainers. For a confidential read of your own estate, check fit for Modernization Shield or email info@evincia.co.