AI Slop Code Risk Monitor

AnalogJ/scrutiny

Name: AnalogJ/scrutiny — Go 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).

Hard Drive S.M.A.R.T Monitoring, Historical Trends & Real World Failure Thresholds

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for AnalogJ/scrutiny, a Go project with 8,384 GitHub stars. SynthScan examined 78,504 lines of code across 471 source files, recording 46 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7

Adjusted Signal

0.7

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

8.4K

Stars

Language

78.5K

Lines of Code

471

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

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

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

PR Review Velocity Impact 3.4/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 1MEDIUM 2LOW 43

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.

Over-Commented Block39 hits · 39 pts

Severity	File	Line	Snippet	Context
LOW	example.scrutiny.yaml	1	# Commented Scrutiny Configuration File	COMMENT
LOW	example.scrutiny.yaml	41	# the `token`	COMMENT
LOW	example.scrutiny.yaml	61	#devices:	COMMENT
LOW	example.scrutiny.yaml	81	#notify:	COMMENT
LOW	example.scrutiny.yaml	101	# - wecom://key	COMMENT
LOW	example.collector.yaml	1	# Commented Scrutiny Configuration File	COMMENT
LOW	example.collector.yaml	21	id: ''	COMMENT
LOW	example.collector.yaml	41	# - device: /dev/bus/0	COMMENT
LOW	example.collector.yaml	61	# commands:	COMMENT
LOW	example.collector.yaml	81	# file: '' #absolute or relative paths allowed, eg. web.log	COMMENT
LOW	example.collector.yaml	101	# The following commented out sections are a preview of additional configuration options that will be available soon.	COMMENT
LOW	webapp/frontend/src/app/layout/layout.component.ts	141	{	COMMENT
LOW	webapp/frontend/src/app/shared/device-status.pipe.ts	41	// determine the device status, by comparing it against the allowed threshold	COMMENT
LOW	webapp/frontend/src/@treo/styles/utilities/_colors.scss	1	// -----------------------------------------------------------------------------------------------------	COMMENT
LOW	webapp/frontend/src/@treo/styles/utilities/_colors.scss	141	// Return the modified theme	COMMENT
LOW	webapp/frontend/src/@treo/styles/utilities/_colors.scss	161	}	COMMENT
LOW	webapp/frontend/src/@treo/styles/utilities/_colors.scss	181	///	COMMENT
LOW	…/frontend/src/@treo/styles/utilities/_breakpoints.scss	1	// -----------------------------------------------------------------------------------------------------	COMMENT
LOW	…p/frontend/src/@treo/styles/utilities/_elevations.scss	1	// -----------------------------------------------------------------------------------------------------	COMMENT
LOW	…bapp/frontend/src/@treo/styles/utilities/_theming.scss	1	// -----------------------------------------------------------------------------------------------------	COMMENT
LOW	webapp/frontend/src/styles/themes.scss	1	// @formatter:off	COMMENT
LOW	webapp/frontend/src/styles/themes.scss	41	// These are generic themes which are useful if you want to adjust the theming of certain container	COMMENT
LOW	webapp/frontend/src/styles/vendors.scss	1	// -----------------------------------------------------------------------------------------------------	COMMENT
LOW	webapp/backend/pkg/database/scrutiny_repository.go	41		COMMENT
LOW	webapp/backend/pkg/database/scrutiny_repository.go	61	//}	COMMENT
LOW	webapp/backend/pkg/web/server_test.go	321	require.Equal(suite.T(), 200, sr.Code)	COMMENT
LOW	webapp/backend/pkg/web/server_test.go	341	// ae := web.AppEngine{	COMMENT
LOW	webapp/backend/pkg/models/device.go	61	func (dv *Device) IsScsi() bool {	COMMENT
LOW	webapp/backend/pkg/models/device.go	81	//	COMMENT
LOW	webapp/backend/pkg/models/device.go	101	// }	COMMENT
LOW	webapp/backend/pkg/models/device.go	121	// }	COMMENT
LOW	webapp/backend/pkg/models/device.go	141	// }	COMMENT
LOW	webapp/backend/pkg/models/device.go	161	// for ndx, attr := range dv.SmartResults[0].ScsiAttributes {	COMMENT
LOW	…backend/pkg/models/measurements/smart_ata_attribute.go	141		COMMENT
LOW	webapp/backend/pkg/errors/errors_test.go	1	package errors_test	COMMENT
LOW	collector/pkg/config/testdata/simple_device.yaml	1	version: 1	COMMENT
LOW	collector/pkg/config/testdata/simple_device.yaml	21	# type:	COMMENT
LOW	collector/pkg/common/shell/local_shell_test.go	41	// bc := collector.BaseCollector {}	COMMENT
LOW	collector/pkg/errors/errors_test.go	1	package errors_test	COMMENT

AI Response Leakage1 hit · 8 pts

Severity	File	Line	Snippet	Context
HIGH	CONTRIBUTING.md	72	### I've implemented a feature	COMMENT

Slop Phrases2 hits · 4 pts

Severity	File	Line	Snippet	Context
MEDIUM	example.collector.yaml	87	# if you need to use a custom base path (for a reverse proxy), you can add a suffix to the endpoint.	COMMENT
LOW	docker/entrypoint-collector.sh	13	# if the cron schedule has been overridden via env variable (eg docker-compose) we should make sure to strip quotes	COMMENT

Modern AI Meta-Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	webapp/frontend/README.md	7	## Code scaffolding	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…backend/pkg/database/scrutiny_repository_migrations.go	568	// Step 1: Create the new bucket. Copy retention rules from the original.	COMMENT

Structural Annotation Overuse1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…backend/pkg/database/scrutiny_repository_migrations.go	568	// Step 1: Create the new bucket. Copy retention rules from the original.	COMMENT

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	…end/src/@treo/lib/mock-api/mock-api.request-handler.ts	7	export class TreoMockApiRequestHandler	CODE