AI Slop Code Risk Monitor

ardalis/CleanArchitecture

Name: ardalis/CleanArchitecture — C# Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Clean Architecture Solution Template: A proven Clean Architecture Template for ASP.NET Core 10

2.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ardalis/CleanArchitecture, a C# project with 18,532 GitHub stars. SynthScan examined 15,994 lines of code across 443 source files, recording 24 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.2 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.2

Adjusted Signal

2.2

Raw Pattern Score

100%

Time Factor

2026-09-21

Last Push

18.5K

Stars

Language

16.0K

Lines of Code

443

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 7.7/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 15 finding(s).

Hallucinated Dependency & Supply Chain Risk 2.8/100 · LOW

Are imports declared and package/API names verified? 9 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 8.7/100 · LOW

Which changes need focused human review? 24 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 1MEDIUM 0LOW 23

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 24 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Structural Annotation Overuse7 hits · 14 pts

Severity	File	Line	Snippet	Context
LOW	docs/content/minimal-clean-architecture.md	233	#### Step 1: Extract Core Project	COMMENT
LOW	docs/content/minimal-clean-architecture.md	246	#### Step 2: Extract Infrastructure Project	COMMENT
LOW	docs/content/minimal-clean-architecture.md	259	#### Step 3: Extract UseCases (Optional)	COMMENT
LOW⚡	docs/content/minimal-clean-architecture.md	271	#### Step 4: Clean Up Web Project	COMMENT
LOW⚡	docs/content/minimal-clean-architecture.md	281	#### Step 1: Merge Projects	COMMENT
LOW⚡	docs/content/minimal-clean-architecture.md	288	#### Step 2: Simplify Patterns	COMMENT
LOW⚡	docs/content/minimal-clean-architecture.md	294	#### Step 3: Organize Vertically	COMMENT

Fake / Example Data9 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	…ple/src/NimblePros.SampleToDo.Web/Contributors/List.cs	24	new(1, "John Doe"),	CODE
LOW	…e/src/NimblePros.SampleToDo.Web/Contributors/Create.cs	30	s.ExampleRequest = new CreateContributorRequest { Name = "John Doe" };	CODE
LOW	…e/src/NimblePros.SampleToDo.Web/Contributors/Create.cs	31	s.ResponseExamples[201] = new CreateContributorResponse(1, "John Doe");	CODE
LOW	…/src/NimblePros.SampleToDo.Web/Contributors/GetById.cs	25	s.ResponseExamples[200] = new ContributorRecord(1, "John Doe");	CODE
LOW	…gate/Handlers/ItemCompletedEmailNotificationHandler.cs	23	await _emailSender.SendEmailAsync("test@test.com", "test@test.com",	CODE
LOW	src/Clean.Architecture.Web/Contributors/List.cs	25	new(1, "John Doe", PhoneNumber.Unknown.ToString()),	CODE
LOW	src/Clean.Architecture.Web/Contributors/Create.cs	31	s.ExampleRequest = new CreateContributorRequest { Name = "John Doe" };	CODE
LOW	src/Clean.Architecture.Web/Contributors/Create.cs	32	s.ResponseExamples[201] = new CreateContributorResponse(1, "John Doe");	CODE
LOW	src/Clean.Architecture.Web/Contributors/GetById.cs	27	s.ResponseExamples[200] = new ContributorRecord(1, "John Doe", "+1 555-555-5555");	CODE

Over-Commented Block7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	…tecture.Web/Infrastructure/Data/AppDbContextFactory.cs	1	using Microsoft.EntityFrameworkCore;	COMMENT
LOW	.github/workflows/publish-templates.yml	61	# dotnet build TestFullTemplate/TestFullTemplate.slnx	COMMENT
LOW	…-validation-unobtrusive/jquery.validate.unobtrusive.js	261	/// <param name="params" type="Array" optional="true">[Optional] An array of parameter names (strings) that will	COMMENT
LOW	…-validation-unobtrusive/jquery.validate.unobtrusive.js	281	/// of adapterName will be used instead.</param>	COMMENT
LOW	…idation-unobtrusive/jquery.validate.unobtrusive.min.js	1	// Unobtrusive validation support library for jQuery and jQuery Validate	COMMENT
LOW	…ntributors/Commands/Delete/DeleteContributorHandler.cs	21	// var aggregateToDelete = await _repository.GetByIdAsync(request.ContributorId);	COMMENT
LOW	src/Clean.Architecture.Web/appsettings.json	21	{	COMMENT

AI Response Leakage1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	docs/content/design-decisions.md	95	Test projects could be organized based on the kind of test (unit, functional, integration, performance, etc.) or by the	CODE