Home / VerifyTests / Verify
AI Slop Code Risk Monitor

VerifyTests/Verify

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

Verify is a snapshot testing tool that simplifies the assertion of complex data models and documents.

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for VerifyTests/Verify, a C# project with 3,473 GitHub stars. SynthScan examined 107,074 lines of code across 3218 source files, recording 162 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.9 (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.9
Adjusted Signal
2.9
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
3.5K
Stars
C#
Language
107.1K
Lines of Code
3.2K
Files
162
Pattern Hits
2026-10-31
Scan Date
0.01
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 12.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 1.4/100 · LOW

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

PR Review Velocity Impact 12.7/100 · LOW

Which changes need focused human review? 162 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 25MEDIUM 2LOW 135

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 162 distinct pattern matches across 5 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.

Synthetic Comment Markers19 hits · 138 pts
SeverityFileLineSnippetContext
HIGH…sAssemblyAttributeAndTestClassInheritance.verified.txt5// This code was generated by a tool.COMMENT
HIGH…sAndAbstractPropertyManuallyDefinedInBase.verified.txt5// This code was generated by a tool.COMMENT
HIGH…ssAndVirtualPropertyManuallyDefinedInBase.verified.txt5// This code was generated by a tool.COMMENT
HIGH…/GlobalNamespaceTests.HasAttributeOnClass.verified.txt5// This code was generated by a tool.COMMENT
HIGH…ibuteOnClassWithGenericsInNestedNamespace.verified.txt5// This code was generated by a tool.COMMENT
HIGH…or.Tests/RecordTests.HasAttributeOnRecord.verified.txt5// This code was generated by a tool.COMMENT
HIGH…dTests.HasAttributeOnClassNestedInRecords.verified.txt5// This code was generated by a tool.COMMENT
HIGH…ceTests.HasBothAssemblyAndClassAttributes.verified.txt5// This code was generated by a tool.COMMENT
HIGH…GlobalNamespaceTests.HasAssemblyAttribute.verified.txt5// This code was generated by a tool.COMMENT
HIGH…sts/RecordTests.HasAttributeOnRecordClass.verified.txt5// This code was generated by a tool.COMMENT
HIGH…Tests.HasAttributeOnBaseAndDerivedClasses.verified.txt5// This code was generated by a tool.COMMENT
HIGH…emblyAttributeAndCustomTestClassAttribute.verified.txt5// This code was generated by a tool.COMMENT
HIGH…/InheritanceTests.HasAttributeOnBaseClass.verified.txt5// This code was generated by a tool.COMMENT
HIGH….Tests/NamespaceTests.HasAttributeOnClass.verified.txt5// This code was generated by a tool.COMMENT
HIGH…estClassOnDerivedAndMarkerAttributeOnBase.verified.txt5// This code was generated by a tool.COMMENT
HIGH…ivedClassAndPropertyManuallyDefinedInBase.verified.txt5// This code was generated by a tool.COMMENT
HIGH…heritanceTests.HasAttributeOnDerivedClass.verified.txt5// This code was generated by a tool.COMMENT
HIGH…icClassTests.TestClassNestedInStaticClass.verified.txt5// This code was generated by a tool.COMMENT
HIGHsrc/Verify.MSTest.SourceGenerator/Emitter.cs8 // This code was generated by a tool.STRING
Over-Commented Block129 hits · 129 pts
SeverityFileLineSnippetContext
LOWsrc/Verify.MSTest/DerivePaths/DerivePathInfo.cs1namespace VerifyMSTest;COMMENT
LOWsrc/Verify.MSTest/DerivePaths/VerifyBase.cs1// ReSharper disable UnusedParameter.LocalCOMMENT
LOWsrc/Verify.TUnit/DerivePaths/DerivePathInfo.cs1namespace VerifyTUnit;COMMENT
LOWsrc/Verify.Expecto.DerivePaths.Tests/Tests.cs61 //COMMENT
LOW…c/StaticSettingsTests/OmitContentFromExceptionTests.cs1public class OmitContentFromExceptionTests :COMMENT
LOW…c/StaticSettingsTests/OmitContentFromExceptionTests.cs21 // }COMMENT
LOWsrc/StaticSettingsTests/EncodingTests.cs1#if DEBUGCOMMENT
LOWsrc/Verify.NUnit.Tests/NugetTests.cs1// #if RELEASE && NET9_0COMMENT
LOWsrc/Verify.NUnit.Tests/NugetTests.cs21// AttributeReader.GetSolutionDirectory(),COMMENT
LOWsrc/Verify/ReceivedMap.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/Counter_Time.cs61#endifCOMMENT
LOWsrc/Verify/TempFile.cs1using IoPath = System.IO.Path;COMMENT
LOWsrc/Verify/TempFile.cs21/// <code>COMMENT
LOWsrc/Verify/TempFile.cs41COMMENT
LOWsrc/Verify/TempFile.cs101 }COMMENT
LOWsrc/Verify/TempFile.cs141 }COMMENT
LOWsrc/Verify/TempFile.cs161 /// </returns>COMMENT
LOWsrc/Verify/TempFile.cs201 /// <param name="extension">COMMENT
LOWsrc/Verify/TempFile.cs221 /// This method is ideal for creating temporary test data files, configuration files, orCOMMENT
LOWsrc/Verify/TempFile.cs261 /// <summary>COMMENT
LOWsrc/Verify/TempFile.cs281 /// This method is suitable for creating temporary files containing binary data such asCOMMENT
LOWsrc/Verify/TempFile.cs321 }COMMENT
LOWsrc/Verify/TempFile.cs341 /// (Explorer on Windows, Finder on macOS), with the file selected.COMMENT
LOWsrc/Verify/TempFile.cs361 /// [Fact]COMMENT
LOWsrc/Verify/TempFile.cs401 /// using var temp = new TempFile(".txt");COMMENT
LOWsrc/Verify/TempFile.cs421 public static implicit operator FileInfo(TempFile temp) =>COMMENT
LOWsrc/Verify/TempDirectory.cs1using IoPath = System.IO.Path;COMMENT
LOWsrc/Verify/TempDirectory.cs41 /// <summary>COMMENT
LOWsrc/Verify/TempDirectory.cs101 /// <summary>COMMENT
LOWsrc/Verify/TempDirectory.cs121 /// <param name="ignoreLockedFiles">COMMENT
LOWsrc/Verify/TempDirectory.cs181 lock (pathsLock)COMMENT
LOWsrc/Verify/TempDirectory.cs201 /// </item>COMMENT
LOWsrc/Verify/TempDirectory.cs221 /// {COMMENT
LOWsrc/Verify/TempDirectory.cs241 /// <returns>The full path to the temporary directory.</returns>COMMENT
LOWsrc/Verify/TempDirectory.cs281 }COMMENT
LOWsrc/Verify/VerifierSettings_Inline.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/VerifierSettings_Inline.cs21 /// </para>COMMENT
LOWsrc/Verify/VerifierSettings_Inline.cs61COMMENT
LOWsrc/Verify/AutoVerify.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/VerifierSettings_PluginConvention.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/VerifierSettings_PluginConvention.cs41 // after its package/project reference was removed. Skip it, rather thanCOMMENT
LOWsrc/Verify/VerifierSettings_PluginConvention.cs61 /// <c>GetReferencedAssemblies()</c> reflects the compiled metadata reference table. The C# compiler omits a referenCOMMENT
LOWsrc/Verify/Inline.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/Target.cs21 internal bool IsSource { get; init; }COMMENT
LOWsrc/Verify/Serialization/VerifyJsonWriter.cs381 // }COMMENT
LOWsrc/Verify/Serialization/Scrubbers/Scrubber.cs1namespace VerifyTests;COMMENT
LOW…ers/VerifySettings_ExtensionMappedInstanceScrubbers.cs61 /// Remove the <see cref="Environment.MachineName" /> from the test results.COMMENT
LOW…ers/VerifySettings_ExtensionMappedInstanceScrubbers.cs121 /// <summary>COMMENT
LOW…ers/VerifySettings_ExtensionMappedInstanceScrubbers.cs141 public void ScrubReplace(string extension, string find, string replacement, StringComparison comparison = StringCompCOMMENT
LOW…ers/VerifierSettings_ExtensionMappedGlobalScrubbers.cs61COMMENT
LOW…ers/VerifierSettings_ExtensionMappedGlobalScrubbers.cs81 public static void ScrubLines(string extension, LineMatch removeLine) =>COMMENT
LOW…ers/VerifierSettings_ExtensionMappedGlobalScrubbers.cs141 /// <paramref name="comparison" /> must be <see cref="StringComparison.Ordinal" /> or <see cref="StringComparison.OrCOMMENT
LOW…ers/VerifierSettings_ExtensionMappedGlobalScrubbers.cs161 /// <summary>COMMENT
LOW…lization/Scrubbers/VerifierSettings_GlobalScrubbers.cs61 /// Remove any lines matching <paramref name="removeLine" /> from the test results.COMMENT
LOW…lization/Scrubbers/VerifierSettings_GlobalScrubbers.cs181 /// Replace every occurrence of <paramref name="find" /> with <paramref name="replacement" />.COMMENT
LOW…Verify/Serialization/Scrubbers/SharedScrubber_Dates.cs201COMMENT
LOW…lization/Scrubbers/VerifySettings_InstanceScrubbers.cs201 /// <summary>COMMENT
LOW…lization/Scrubbers/VerifySettings_InstanceScrubbers.cs221 /// Replace every occurrence of each Find with its Replacement.COMMENT
LOWsrc/Verify/Serialization/Scrubbers/GuidFormats.cs1namespace VerifyTests;COMMENT
LOWsrc/Verify/Splitters/Settings_ExcludeTargets.cs41COMMENT
69 more matches not shown…
Cross-File Repetition6 hits · 30 pts
SeverityFileLineSnippetContext
HIGHdocs/naming.md0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
HIGHsrc/Verify.NUnit.Tests/Snippets/ExtensionSample.cs0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
HIGHsrc/Verify.XunitV3.Tests/Snippets/ExtensionSample.cs0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
HIGHsrc/Verify.MSTest.Tests/Snippets/ExtensionSample.cs0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
HIGHsrc/Verify.TUnit.Tests/Snippets/ExtensionSample.cs0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
HIGHsrc/Verify.Fixie.Tests/Snippets/ExtensionSample.cs0<note> <to>joe</to> <from>kim</from> <heading>reminder</heading> </note>STRING
Structural Annotation Overuse6 hits · 9 pts
SeverityFileLineSnippetContext
LOWdocs/ai-usage.md46### Step 1: Read the exception messageCOMMENT
LOWdocs/ai-usage.md101### Step 2: Read the filesCOMMENT
LOWdocs/ai-usage.md109### Step 3: Determine the actionCOMMENT
LOWdocs/mdsource/ai-usage.source.md39### Step 1: Read the exception messageCOMMENT
LOWdocs/mdsource/ai-usage.source.md94### Step 2: Read the filesCOMMENT
LOWdocs/mdsource/ai-usage.source.md102### Step 3: Determine the actionCOMMENT
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMreadme.md1011* [Accessibilité, Azure Storage Action, Golden Master et Agentic AI (15 Jan 2025)](https://devdevdev.net/tr01-2025-accesCOMMENT
MEDIUMreadme.source.md420* [Accessibilité, Azure Storage Action, Golden Master et Agentic AI (15 Jan 2025)](https://devdevdev.net/tr01-2025-accesCOMMENT