AI Slop Code Risk Monitor

agda/agda

Name: agda/agda — Haskell 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).

Agda is a dependently typed programming language / interactive theorem prover.

1.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for agda/agda, a Haskell project with 2,962 GitHub stars. SynthScan examined 39,792 lines of code across 284 source files, recording 31 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.1

Adjusted Signal

1.1

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

3.0K

Stars

Haskell

Language

39.8K

Lines of Code

284

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

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

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

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 31 distinct pattern matches across 6 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 Block23 hits · 23 pts

Severity	File	Line	Snippet	Context
LOW	fix-whitespace.yaml	1	# This file contains the project-specific settings for `fix-whitespace` a tiny	COMMENT
LOW	.readthedocs.yaml	1	# .readthedocs.yaml	COMMENT
LOW	ecosystem/plfa-test.sh	1	#!/bin/sh	COMMENT
LOW	test/test-suite-covers-errors.sh	1	#!/bin/sh	COMMENT
LOW	test/test-suite-covers-warnings.sh	1	#!/bin/sh	COMMENT
LOW	test/Interaction/Issue4828.sh	1	#!/bin/sh	COMMENT
LOW	.github/actionlint.yaml	1	self-hosted-runner:	COMMENT
LOW	doc/user-manual/conf.py	1	# -- coding: utf-8 --	COMMENT
LOW	doc/user-manual/conf.py	81	# Andreas, 2024-10-10: the following line is not needed since sphinx_rtd_theme-0.2.5	COMMENT
LOW	doc/user-manual/conf.py	101	# relative to this directory. They are copied after the builtin static files,	COMMENT
LOW	doc/user-manual/conf.py	121		COMMENT
LOW	src/github/workflows/test.yml	161	# We include stack-${GHC_VER}.yaml in the primary cache key so that the cache gets rewritten	COMMENT
LOW	src/github/workflows/test.yml	321	- name: "Successful tests using the standard library"	COMMENT
LOW	src/github/workflows/test.yml	401		COMMENT
LOW	src/github/workflows/test.yml	441	# # These jobs take up to 10 min each, so we do not run them on	COMMENT
LOW	src/github/workflows/test.yml	481	run: make ${{ matrix.library }}-test	COMMENT
LOW	src/github/workflows/test.yml	501	# - name: "Run tests for the size solver"	COMMENT
LOW	src/github/workflows/deploy.yml	181	if: ${{ runner.os == 'Windows' }}	COMMENT
LOW	src/github/workflows/deploy.yml	201		COMMENT
LOW	src/github/workflows/cabal.yml	241		COMMENT
LOW	src/github/workflows/header.txt	1	######################################################	COMMENT
LOW	src/data/JS/agda-rts.amd.js	1	define([], function() {	COMMENT
LOW	src/data/JS/agda-rts.js	1	// Contains most of the primitives required by the JavaScript backend.	COMMENT

Self-Referential Comments4 hits · 12 pts

Severity	File	Line	Snippet	Context
MEDIUM	fix-whitespace.yaml	1	# This file contains the project-specific settings for `fix-whitespace` a tiny	COMMENT
MEDIUM	test/Interaction/Issue2574ImportBlank.sh	3	# This file is intentionally left empty.	COMMENT
MEDIUM	test/Interaction/Issue2574Import.sh	3	# This file is intentionally left empty.	COMMENT
MEDIUM	test/Interaction/Issue8647.sh	22	# Create a unique named pipe	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/github/workflows/test.yml	11	# Include everything at first (more robust wrt. additions to the repo).	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	src/github/workflows/test.yml	80	# Step 1: Building Agda	COMMENT

Structural Annotation Overuse1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	src/github/workflows/test.yml	80	# Step 1: Building Agda	COMMENT

Deep Nesting1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	test/check-filename-case-clashes.py	53		CODE