AI Slop Code Risk Monitor

google/guice

Name: google/guice — 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).

Guice (pronounced 'juice') is a lightweight dependency injection framework for Java 11 and above, brought to you by Google.

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for google/guice, a Java project with 12,729 GitHub stars. SynthScan examined 119,037 lines of code across 708 source files, recording 26 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5

Adjusted Signal

0.5

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

12.7K

Stars

Java

Language

119.0K

Lines of Code

708

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

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

Hallucinated Dependency & Supply Chain Risk 1.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 2.2/100 · LOW

Which changes need focused human review? 26 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 2HIGH 0MEDIUM 5LOW 19

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

Hallucination Indicators2 hits · 20 pts

Severity	File	Line	Snippet	Context
CRITICAL	…/test/com/google/inject/name/NamedEquivalanceTest.java	395	+ com.google.inject.name.Named.class.getName()	CODE
CRITICAL	core/src/com/google/inject/ConfigurationException.java	39	this.messages = com.google.common.collect.ImmutableSet.copyOf(messages);	CODE

AI Slop Vocabulary5 hits · 15 pts

Severity	File	Line	Snippet	Context
MEDIUM	…e/src/com/google/inject/internal/BindingProcessor.java	137	// here, we can leverage faster `InternalFactory` implementations.	COMMENT
MEDIUM	core/src/com/google/inject/internal/InjectorShell.java	223	// we leverage those bindings if they exist.	COMMENT
MEDIUM	…/google/inject/internal/InjectionRequestProcessor.java	159	// 3. Can leverage or initialize caches for transitive InternalFactory.getHandle	COMMENT
MEDIUM	core/src/com/google/inject/internal/InjectorImpl.java	1161	// Access off the BindingImpl to leverage the cached provider.	COMMENT
MEDIUM	core/src/com/google/inject/internal/InjectorImpl.java	1173	// that getProvider can leverage the cache inside BindingImpl	COMMENT

Over-Commented Block11 hits · 11 pts

Severity	File	Line	Snippet	Context
LOW	core/test/com/google/inject/CircularDependencyTest.java	661	bind(I.class).to(IImpl.class);	COMMENT
LOW	core/test/com/google/inject/CircularDependencyTest.java	921	+ " dependencies are disabled");	COMMENT
LOW	core/test/com/googlecode/guice/JakartaTest.java	261		COMMENT
LOW	…om/google/inject/internal/ProviderInternalFactory.java	101	// `circularGetHandleImmediate` then the order would be reversed since the provision callback	COMMENT
LOW	…re/src/com/google/inject/internal/InternalContext.java	61	// collisions are relatively cheap.	COMMENT
LOW	…/com/google/inject/internal/PackageNameCompressor.java	61	private static final Pattern CLASSNAME_PATTERN =	COMMENT
LOW	…/google/inject/internal/InjectionRequestProcessor.java	141	InternalContext context = injector.enterContext();	COMMENT
LOW	core/src/com/google/inject/internal/ProviderMethod.java	381	@Override	COMMENT
LOW	core/src/com/google/inject/internal/InjectorImpl.java	281	} else {	COMMENT
LOW	core/src/com/google/inject/internal/InjectorImpl.java	681		COMMENT
LOW	…et/test/com/google/inject/servlet/ContextPathTest.java	121	//	COMMENT

Fake / Example Data4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	…est/com/google/inject/RestrictedBindingSourceTest.java	491	return "lorem ipsum";	CODE
LOW	…est/com/google/inject/RestrictedBindingSourceTest.java	525	return "lorem ipsum";	CODE
LOW	…est/com/google/inject/RestrictedBindingSourceTest.java	555	return "lorem ipsum";	CODE
LOW	…est/com/google/inject/RestrictedBindingSourceTest.java	587	return "lorem ipsum";	CODE

Verbosity Indicators2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	…re/src/com/google/inject/internal/InternalContext.java	476	// now we need to check if we can proxy the class	COMMENT
LOW	…/com/google/inject/internal/ProviderMethodsModule.java	148	// We have found some provider methods, now we need to check if any were overridden.	COMMENT

TODO Padding1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…gle/inject/servlet/TransferRequestIntegrationTest.java	34	// TODO: Add test for HTTP transferring.	COMMENT

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	…ogle/inject/errors/MissingImplementationErrorTest.java	80	static class RequestHandler {	CODE