AI Slop Code Risk Monitor

cobusgreyling/loop-engineering

SlopCodeMonitor badge for cobusgreyling/loop-engineering Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.

3.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cobusgreyling/loop-engineering, a TypeScript project with 11,675 GitHub stars. SynthScan examined 40,853 lines of code across 506 source files, recording 46 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 3.1 (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.

3.1
Adjusted Signal
3.1
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
11.7K
Stars
TypeScript
Language
40.9K
Lines of Code
506
Files
46
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 5.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 9.2/100 · LOW

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

PR Review Velocity Impact 15.5/100 · LOW

Which changes need focused human review? 46 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 6MEDIUM 31LOW 9

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

Decorative Section Separators15 hits · 44 pts
SeverityFileLineSnippetContext
MEDIUMtools/loop-drill/src/drill.ts109// ── Glob → concrete sample path ────────────────────────────────────COMMENT
MEDIUMtools/loop-drill/src/drill.ts135// ── Gate drills (Over-Reach) ───────────────────────────────────────COMMENT
MEDIUMtools/loop-drill/src/drill.ts265// ── Circuit breaker drills (Infinite Fix Loop / Token Burn) ────────COMMENT
MEDIUMtools/loop-drill/src/drill.ts458// ── Report assembly ────────────────────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts34// ── Resources ──────────────────────────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts138// ── Resource Templates (dynamic) ───────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts200// ── Tools ──────────────────────────────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts549// ── Start ──────────────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts85// ── Config validation ──────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts129// ── Error normalization ────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts180// ── Circuit breaker ────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts316// ── Pruning ────────────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts364// ── Summarization ──────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts427// ── Injection ──────────────────────────────────────────────────────COMMENT
MEDIUM…ources/ky-cut-surface-philosophy-v0_1/TERMINAL_ART.txt1┌──[ KUNST-TERMINALEN // KY CUT SURFACE v0.1 ]──────────────────────────────┐CODE
Modern AI Meta-Vocabulary13 hits · 34 pts
SeverityFileLineSnippetContext
MEDIUMtools/loop-swarm/README.md18See [Quickstart](../../docs/QUICKSTART.md#multi-agent-consensus-sandboxing-loop-swarm) for workflow examples and commandCODE
MEDIUMtools/loop-sync/README.md52# Preview what --auto-fix would scaffold/change, without writing anythingCOMMENT
MEDIUMtools/loop-audit/src/auditor.ts887 // Proof that guardrails fire, from loop-drill --record.COMMENT
MEDIUM⚡tools/loop-audit/src/cli.ts99 console.log(' # Or scaffold automatically:');CODE
MEDIUM⚡tools/loop-audit/src/cli.ts108 console.log(' # IMPORTANT (v1.4): After scaffolding, actually RUN a loop (report-only) and commit the updated STATECODE
MEDIUM⚡tools/loop-audit/src/cli.ts111 console.log(' # L3: prove the guardrails fire, not just exist, then commit the record');CODE
MEDIUMdocs/QUICKSTART.md17Not sure which loop? Use the [interactive pattern picker](https://cobusgreyling.github.io/loop-engineering/#interactive)CODE
MEDIUMdocs/QUICKSTART.md17Not sure which loop? Use the [interactive pattern picker](https://cobusgreyling.github.io/loop-engineering/#interactive)CODE
MEDIUMdocs/QUICKSTART.md355# Run multi-agent consensus across 3 sequential sandboxesCOMMENT
MEDIUMdocs/safety.md136- `loop-swarm`: Multi-agent consensus sandboxing across sequential `loop-sandbox` runs. Requires byte-identical patch coCODE
MEDIUMdocs/RELEASE.md104# goal-init (scaffold goal engineering setups)COMMENT
MEDIUMexamples/codex/issue-triage.md36Install `issue-triage` per [Codex Agent Skills](https://developers.openai.com/codex/skills) — scaffold with `loop-init` CODE
MEDIUMexamples/github-actions/ci-sweeper.yml1# CI Sweeper — event-driven on workflow failureCOMMENT
Cross-File Repetition6 hits · 30 pts
SeverityFileLineSnippetContext
HIGHstarters/minimal-loop-codex/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/ci-sweeper/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/pr-babysitter/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/issue-triage/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/post-merge-cleanup/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/dependency-sweeper/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
AI Slop Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUM⚡tools/loop-audit/src/cli.ts105 console.log(' # or: npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage');CODE
MEDIUMexamples/github-actions/daily-triage.yml2# Invokes your agent harness with a triage prompt. Adapt the "Run agent" stepCOMMENT
MEDIUMexamples/github-actions/issue-triage.yml3# issue-triage-state.md. Wire the "Run triage agent" step to your harness.COMMENT
Hyper-Verbose Identifiers5 hits · 5 pts
SeverityFileLineSnippetContext
LOWtools/loop-init/src/cli.ts254function cheaperinferenceInterfaceYaml(model: string): string {CODE
LOWtools/loop-context/src/budget-resolver.ts13export function assertValidBudgetScenario(scenario: string): asserts scenario is BudgetScenario {CODE
LOWtools/loop-context/src/budget-resolver.ts106export async function resolveTokenBudgetFromPattern(input: BudgetFromPatternInput): Promise<number> {CODE
LOWtools/loop-context/src/budget-resolver.ts126export async function resolveDailyBudgetFromPattern(input: BudgetFromPatternInput): Promise<number> {CODE
LOWtools/loop-context/src/context-manager.ts95export function assertSimilarityThreshold(value: unknown, label = 'similarityThreshold'): asserts value is number {CODE
Unused Imports3 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/generate-star-history.py13CODE
LOWscripts/generate-audit-demo-gif.py4CODE
LOWscripts/generate-audit-demo-gif.py7CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtools/loop-sandbox/src/sandbox.ts81 // Cleanup must run on every exit path, including Ctrl+C mid-run, andCOMMENT