AI Slop Code Risk Monitor

Microsoft365DSC/Microsoft365DSC

Name: Microsoft365DSC/Microsoft365DSC — PowerShell 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).

Manages, configures, extracts and monitors Microsoft 365 tenant configurations

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Microsoft365DSC/Microsoft365DSC, a PowerShell project with 2,439 GitHub stars. SynthScan examined 150,876 lines of code across 1394 source files, recording 40 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.

0.3

Adjusted Signal

0.3

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

2.4K

Stars

PowerShell

Language

150.9K

Lines of Code

1.4K

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 1.6/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 40 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 0.0/100 · LOW

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

PR Review Velocity Impact 1.8/100 · LOW

Which changes need focused human review? 40 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 5LOW 34

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 40 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.

Over-Commented Block34 hits · 34 pts

Severity	File	Line	Snippet	Context
LOW	src/Microsoft365DSC.Intune/SettingValueResolver.cs	21	/// The resolved value. Can be a single string/int or an array (string[]/int[]).	COMMENT
LOW	…Microsoft365DSC.Intune/SettingCatalogPolicyExporter.cs	221	#region Property access helpers	COMMENT
LOW	…Microsoft365DSC.Intune/SettingCatalogPolicyExporter.cs	241	/// PowerShell. This class only handles the data transformation.</item>	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingDefinitionOption.cs	21	/// <summary>	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingDefinitionOption.cs	41	/// </summary>	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingsCatalogHelper.cs	21	public string Name { get; set; }	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingsCatalogHelper.cs	41	/// Maximum number of instances allowed for this setting (from maximumCount).	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingsCatalogHelper.cs	301	///	COMMENT
LOW	src/Microsoft365DSC.Intune/SettingsCatalogHelper.cs	361	/// <summary>	COMMENT
LOW	…/Microsoft365DSC.Intune/SettingInstanceTemplateInfo.cs	21		COMMENT
LOW	…/Microsoft365DSC.Intune/SettingInstanceTemplateInfo.cs	41	/// (edge case: ThreatTypeSettings in IntuneAntivirusPolicyLinux).	COMMENT
LOW	…/Microsoft365DSC.Intune/SettingInstanceTemplateInfo.cs	61	/// Corresponds to the objects returned by <c>Get-MgBetaDeviceManagementConfigurationPolicyTemplateSettingTemplate</	COMMENT
LOW	…oft365DSC.Intune/SettingCatalogPolicySettingBuilder.cs	1	using System;	COMMENT
LOW	src/Microsoft365DSC.Connection/ConnectionHelper.cs	1	using System;	COMMENT
LOW	src/Microsoft365DSC.Utilities/MemberAccessor.cs	1	using System;	COMMENT
LOW	src/Microsoft365DSC.Utilities/Utilities.cs	61	{	COMMENT
LOW	src/Microsoft365DSC.Compare/ResourceComparer.cs	21		COMMENT
LOW	src/Microsoft365DSC.Compare/ResourceComparer.cs	401	/// Result object for ResourceComparer.Compare.	COMMENT
LOW	src/Microsoft365DSC.Compare/CompareRules.cs	41	/// </summary>	COMMENT
LOW	src/Microsoft365DSC.Compare/ConfigurationComparer.cs	21		COMMENT
LOW	src/Microsoft365DSC.Relations/ExportRelationSession.cs	1	using Microsoft365DSC.Utilities;	COMMENT
LOW	src/Microsoft365DSC.Relations/ExportRelationSession.cs	41	/// <exception cref="ArgumentNullException">The index is null.</exception>	COMMENT
LOW	src/Microsoft365DSC.Relations/ExportRelationSession.cs	101	}	COMMENT
LOW	src/Microsoft365DSC.Relations/ExportInstanceNames.cs	1	using System;	COMMENT
LOW	src/Microsoft365DSC.Relations/ExportInstanceNames.cs	21	/// free and then both take it.	COMMENT
LOW	src/Microsoft365DSC.Relations/RelationDefinition.cs	21	/// The property on the target resource that the key matches against, or null to fall	COMMENT
LOW	src/Microsoft365DSC.Relations/RelationResolver.cs	181		COMMENT
LOW	src/Microsoft365DSC.Relations/DependsOnInjector.cs	21	/// resource name to a collection of property names.	COMMENT
LOW	src/Microsoft365DSC.Relations/DependsOnInjector.cs	281	return builder.ToString();	COMMENT
LOW	src/Microsoft365DSC.Relations/DependsOnInjector.cs	701	/// <param name="reference">The candidate instance reference.</param>	COMMENT
LOW	src/Microsoft365DSC.Relations/ExportModel.cs	81	/// Null when no relation targets this resource type by a named property. Populated from	COMMENT
LOW	src/Microsoft365DSC.Relations/RelationIndex.cs	81	new(StringComparer.OrdinalIgnoreCase);	COMMENT
LOW	src/Microsoft365DSC.Reporting/ReportRequest.cs	21	/// The root of the Microsoft365DSC module, used to resolve the resource metadata a	COMMENT
LOW	…soft365DSC.Reporting/Configuration/ResourceMetadata.cs	41	/// Returns the class of the given name, or null when the schema does not define it.	COMMENT

AI Slop Vocabulary4 hits · 8 pts

Severity	File	Line	Snippet	Context
MEDIUM	…ecurityBaselineDefenderForEndpoint.policySettings.json	1	[{"settingDefinitions":[{"settingUsage":"configuration","occurrence":{"minDeviceOccurrence":0,"maxDeviceOccurrence":1},"	CODE
MEDIUM	…ecurityBaselineDefenderForEndpoint.policySettings.json	1	[{"settingDefinitions":[{"settingUsage":"configuration","occurrence":{"minDeviceOccurrence":0,"maxDeviceOccurrence":1},"	CODE
MEDIUM	…urityBaselineDefenderForEndpoint.settingTemplates.json	1	[{"settingDefinitions":[{"settingUsage":"configuration","occurrence":{"minDeviceOccurrence":0,"maxDeviceOccurrence":1},"	CODE
MEDIUM	…urityBaselineDefenderForEndpoint.settingTemplates.json	1	[{"settingDefinitions":[{"settingUsage":"configuration","occurrence":{"minDeviceOccurrence":0,"maxDeviceOccurrence":1},"	CODE

AI Response Leakage1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	…og/2026/class-based-resources/class-based-resources.md	110	The formal proposal came in June 2025 with issue [#6202](https://github.com/Microsoft365DSC/Microsoft365DSC/issues/6202)	CODE

Modern AI Meta-Vocabulary1 hit · 2 pts

Severity	File	Line	Snippet	Context
MEDIUM	…6/performance-improvements/performance-improvements.md	96	Microsoft365DSC is a hybrid module. Some of the code is written in C# and compiled into assemblies, while some of it is	CODE