AI Slop Code Risk Monitor

google/styleguide

Name: google/styleguide — Emacs Lisp 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).

Style guides for Google-originated open-source projects

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for google/styleguide, a Emacs Lisp project with 39,781 GitHub stars. SynthScan examined 52,402 lines of code across 41 source files, recording 10 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.4 (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.4

Adjusted Signal

0.4

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

39.8K

Stars

Emacs Lisp

Language

52.4K

Lines of Code

Files

Pattern Hits

2026-10-31

Scan Date

0.07

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

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

Hallucinated Dependency & Supply Chain Risk 0.3/100 · LOW

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

Agent Over-Engineering Ratio 0.1/100 · LOW

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

PR Review Velocity Impact 2.4/100 · LOW

Which changes need focused human review? 10 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 3MEDIUM 0LOW 7

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

Docstring Block Structure3 hits · 15 pts

Severity	File	Line	Snippet	Context
HIGH	pyguide.md	371	Connects to the next available port. Args: minimum: A port value greater or equal to 1024. R	STRING
HIGH	pyguide.md	2222	`). Certain aspects of a function should be documented in special sections, listed below. Each section begins with a he	STRING
HIGH	pyguide.md	2248	`) and the opening sentence is sufficient to describe the return value. Do not imitate older 'NumPy style'	STRING

Over-Commented Block4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	shellguide.md	201	# None	COMMENT
LOW	shellguide.md	601	git send-email --to "${reviewers}" ${ccs:+"--cc" "${ccs}"}	COMMENT
LOW	go/best-practices.md	1741		COMMENT
LOW	go/decisions.md	561	```text	COMMENT

Fake / Example Data2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	tsguide.md	165	* @fileoverview Description of file. Lorem ipsum dolor sit amet, consectetur	COMMENT
LOW	tsguide.md	165	* @fileoverview Description of file. Lorem ipsum dolor sit amet, consectetur	COMMENT

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	pyguide.md	2358	def read_from_remote_filesystem(url: str) -> Iterator[RemoteFile]:	CODE