AI Slop Code Risk Monitor

dropwizard/metrics

Name: dropwizard/metrics — Java 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).

:chart_with_upwards_trend: Capturing JVM- and application-level metrics. So you know what's going on.

0.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for dropwizard/metrics, a Java project with 7,846 GitHub stars. SynthScan examined 60,165 lines of code across 542 source files, recording 27 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.6

Adjusted Signal

0.6

Raw Pattern Score

100%

Time Factor

2026-10-26

Last Push

7.8K

Stars

Java

Language

60.2K

Lines of Code

542

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

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

Hallucinated Dependency & Supply Chain Risk 0.3/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 2.7/100 · LOW

Which changes need focused human review? 27 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 3LOW 24

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 27 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 Block18 hits · 18 pts

Severity	File	Line	Snippet	Context
LOW	.gitpod.yml	1	## Learn more about this file at 'https://www.gitpod.io/docs/references/gitpod-yml'	COMMENT
LOW	.gitpod.yml	21		COMMENT
LOW	.gitpod.yml	41	## The 'tasks' section defines how Gitpod prepares and builds this project	COMMENT
LOW	.gitpod.yml	61	# # to a custom Dockerfile to make prebuilds faster	COMMENT
LOW	.gitpod.yml	81	# lynx `gp url`	COMMENT
LOW	.gitpod.yml	101	## and extensions can be added by sending a pull-request with the extension	COMMENT
LOW	docs/source/conf.py	1	# -- coding: utf-8 --	COMMENT
LOW	docs/source/conf.py	41		COMMENT
LOW	docs/source/conf.py	61	#today = ''	COMMENT
LOW	docs/source/conf.py	81	#show_authors = False	COMMENT
LOW	docs/source/conf.py	121	#html_short_title = None	COMMENT
LOW	docs/source/conf.py	141	# If true, SmartyPants will be used to convert quotes and dashes to	COMMENT
LOW	docs/source/conf.py	161	#html_split_index = False	COMMENT
LOW	docs/source/conf.py	201	latex_documents = [	COMMENT
LOW	docs/source/conf.py	261	# -- Options for Epub output ---------------------------------------------------	COMMENT
LOW	docs/source/conf.py	281	#epub_uid = ''	COMMENT
LOW	docs/source/_themes/metrics/less/grid.less	1	// GRID SYSTEM	COMMENT
LOW	docs/source/_themes/metrics/less/sprites.less	1	// SPRITES	COMMENT

AI Slop Vocabulary2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	…zard/metrics/jetty12/ee10/AbstractIntegrationTest.java	29	// the ServletContextHandler is needed to utilize servlet related classes	COMMENT
MEDIUM	…zard/metrics/jetty12/ee11/AbstractIntegrationTest.java	29	// the ServletContextHandler is needed to utilize servlet related classes	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	docs/source/conf.py	6	# This file is execfile()d with the current directory set to its containing dir.	COMMENT

Fake / Example Data2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	…/codahale/metrics/jdbi3/InstrumentedSqlLoggerTest.java	27	final String statementName = "my-fake-name";	CODE
LOW	…/codahale/metrics/jdbi3/InstrumentedSqlLoggerTest.java	49	final String statementName = "my-fake-name";	CODE

Unused Imports2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	docs/source/conf.py	14		CODE
LOW	docs/source/conf.py	14		CODE

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…rics/jdbi3/strategies/TimedAnnotationNameStrategy.java	33	// We need to check if the class has a custom timer name	COMMENT

Slop Phrases1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	docs/source/_themes/metrics/less/forms.less	178	// But don't forget to remove their padding on first-child	COMMENT