Home / mgth / LittleBigMouse
AI Slop Code Risk Monitor

mgth/LittleBigMouse

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

DPI Aware mouse move across screens

2.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for mgth/LittleBigMouse, a C# project with 6,722 GitHub stars. SynthScan examined 132,346 lines of code across 833 source files, recording 342 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 2.6 (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.6
Adjusted Signal
2.6
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
6.7K
Stars
C#
Language
132.3K
Lines of Code
833
Files
342
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 12.4/100 · LOW

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

Which changes need focused human review? 342 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 0MEDIUM 4LOW 338

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 342 distinct pattern matches across 2 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 Block338 hits · 338 pts
SeverityFileLineSnippetContext
LOWrun-lbm.sh1#!/usr/bin/env bashCOMMENT
LOWrun-lbm.sh61# when git or the tags are unavailable.COMMENT
LOWrun-lbm.sh81# ORDER AND WAITING BOTH MATTER, and for the same reason: the UI relaunches theCOMMENT
LOW…eBigMouse.Core/LittleBigMouse.DisplayLayout/IniFile.cs41 string key, string def, StringBuilder retVal,COMMENT
LOW…eBigMouse.Core/LittleBigMouse.DisplayLayout/PnpName.cs21 http://www.mgth.frCOMMENT
LOW…LittleBigMouse.DisplayLayout/Monitors/DisplaySource.cs61 /// </summary>COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/PhysicalSource.cs21COMMENT
LOW…ttleBigMouse.DisplayLayout/Monitors/PhysicalMonitor.cs181 //[DataMember]COMMENT
LOW…ttleBigMouse.DisplayLayout/Monitors/PhysicalMonitor.cs221 /// <summary>COMMENT
LOW…ttleBigMouse.DisplayLayout/Monitors/PhysicalMonitor.cs241 /// </summary>COMMENT
LOW…BigMouse.DisplayLayout/Monitors/MonitorBorderPolicy.cs21/// its values, so the first switch to "PerMonitor" starts from what the user currently sees;</item>COMMENT
LOW…BigMouse.DisplayLayout/Monitors/MonitorBorderPolicy.cs141 /// </summary>COMMENT
LOW…ouse.DisplayLayout/Monitors/ExcludedProcessDefaults.cs1using System;COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs81 /// DISPLAY SURFACE shared along the contact edge — bezels excluded, they cannot carry theCOMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs101 bool LoopX { get; set; }COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs121 /// <summary>COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs141 /// - CrossCOMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs161COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs181COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs201COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs221COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/ILayoutOptions.cs241COMMENT
LOW…ittleBigMouse.DisplayLayout/Monitors/MonitorsLayout.cs121 set => this.RaiseAndSetIfChanged(ref field, value);COMMENT
LOW…se.DisplayLayout/Monitors/Extensions/LayoutGeometry.cs21/// pixel span the system gives that same panel, the shared part of two spans.COMMENT
LOW…se.DisplayLayout/Monitors/Extensions/LayoutGeometry.cs81COMMENT
LOW…se.DisplayLayout/Monitors/Extensions/LayoutGeometry.cs141/// </para>COMMENT
LOW…se.DisplayLayout/Monitors/Extensions/LayoutGeometry.cs161 /// <summary>COMMENT
LOW…se.DisplayLayout/Monitors/Extensions/LayoutGeometry.cs201COMMENT
LOW…ayout/Monitors/Extensions/MonitorSnapshotExtensions.cs1#nullable enableCOMMENT
LOW….DisplayLayout/Monitors/Extensions/CompactionSolver.cs1#nullable enableCOMMENT
LOW….DisplayLayout/Monitors/Extensions/CompactionSolver.cs21/// The layout options compaction obeys, snapshotted so the solve is a pure function.COMMENT
LOW….DisplayLayout/Monitors/Extensions/CompactionSolver.cs41/// On top of that, <see cref="CompactionOptions.MinimalEdgeOverlap"/> demands a crossingCOMMENT
LOW…splayLayout/Monitors/Extensions/PixelLocationSolver.cs1#nullable enableCOMMENT
LOW…playLayout/Monitors/Extensions/SystemLocationSolver.cs1#nullable enableCOMMENT
LOW…playLayout/Monitors/Extensions/SystemLocationSolver.cs21/// </summary>COMMENT
LOW…playLayout/Monitors/Extensions/SystemLocationSolver.cs101 }COMMENT
LOW…playLayout/Monitors/Extensions/SystemLocationSolver.cs141 /// <summary>COMMENT
LOW…rs/Extensions/MonitorsLocationsFromSystemExtensions.cs41 }COMMENT
LOW…/LittleBigMouse.DisplayLayout/Dimensions/BorderSide.cs41 /// <summary>COMMENT
LOW…se.DisplayLayout.Tests/LocationSolverRoundTripTests.cs1using HLab.Geo;COMMENT
LOW…se.DisplayLayout.Tests/LocationSolverRoundTripTests.cs341COMMENT
LOW…se.DisplayLayout.Tests/WindowsWallpaperWatcherTests.cs1using System;COMMENT
LOW…use.DisplayLayout.Tests/WindowsWallpaperReaderTests.cs1using HLab.Geo;COMMENT
LOW…LittleBigMouse.DisplayLayout.Tests/DisplayDumpTests.cs1using LittleBigMouse.DisplayLayout.Tests.DomainOracle;COMMENT
LOW…gMouse.DisplayLayout.Tests/RegistryLayoutStoreTests.cs1using System.Globalization;COMMENT
LOW…igMouse.DisplayLayout.Tests/WireContractGoldenTests.cs1using DynamicData;COMMENT
LOW…igMouse.DisplayLayout.Tests/WireContractGoldenTests.cs21/// the C# member names, so renaming a property here silently renames a wire attribute.COMMENT
LOW…igMouse.DisplayLayout.Tests/WireContractGoldenTests.cs81COMMENT
LOW…igMouse.DisplayLayout.Tests/WireContractGoldenTests.cs241 /// "CornerCrossing"; everything else it reads as "Strait", silently. The alias existsCOMMENT
LOW…ittleBigMouse.DisplayLayout.Tests/DomainOracleTests.cs1using System.Reflection;COMMENT
LOW…ittleBigMouse.DisplayLayout.Tests/DomainOracleTests.cs21/// See <c>domain-oracle/README.md</c> — including for what a failure here means (a behaviourCOMMENT
LOW…se.DisplayLayout.Tests/LayoutPersistenceGoldenTests.cs1using DynamicData;COMMENT
LOW…se.DisplayLayout.Tests/LayoutPersistenceGoldenTests.cs21/// <para>COMMENT
LOW…gMouse.DisplayLayout.Tests/DomainOracle/OracleInput.cs21 public string? Description { get; init; }COMMENT
LOW…gMouse.DisplayLayout.Tests/DomainOracle/DisplayDump.cs21/// recorded corpus cannot make, since it starts after discovery.COMMENT
LOW…BigMouse.DisplayLayout.Tests/DomainOracle/OracleRun.cs81 }COMMENT
LOW…leBigMouse.Core/LittleBigMouse.Zones/RectExtensions.cs101 // No direct path, return the source rectangleCOMMENT
LOW…igMouse.Core/LittleBigMouse.Zones/IBorderResistance.cs1namespace LittleBigMouse.Zoning;COMMENT
LOW…se.Core/LittleBigMouse.Zones/ILittleBigMouseService.cs41 // Outcome of a Load command: the daemon parsed the zones into its engine (payload is anCOMMENT
LOWrust/Cargo.toml1# The Rust side of LittleBigMouse, as one Cargo workspace.COMMENT
278 more matches not shown…
AI Slop Vocabulary4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMrust/crates/lbm-hook/Cargo.toml81# criterion harness: allocation counts are deterministic, so they are reportedCOMMENT
MEDIUMrust/crates/lbm-hook/src/daemon/mod.rs268/// second click restarted it. Re-asserting the flag makes the swap seamlessCOMMENT
MEDIUMrust/crates/lbm-store/src/layout_migrations.rs123/// value — the portrait/landscape signal is robust to user-customized magnitudes (editsCOMMENT
MEDIUM…eBigMouse.Plugins.Core/Persistence/LayoutMigrations.cs124 /// signal is robust to user-customized magnitudes (edits keep the panel aspect viaCOMMENT