AI Slop Code Risk Monitor

DenverCoder1/github-readme-streak-stats

Name: DenverCoder1/github-readme-streak-stats — PHP 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).

🔥 Stay motivated and show off your contribution streak! 🌟 Display your total contributions, current streak, and longest streak on your GitHub profile README

4.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for DenverCoder1/github-readme-streak-stats, a PHP project with 7,185 GitHub stars. SynthScan examined 9,741 lines of code across 54 source files, recording 36 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 4.2 (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.

4.2

Adjusted Signal

4.2

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

7.2K

Stars

PHP

Language

9.7K

Lines of Code

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

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

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

PR Review Velocity Impact 16.9/100 · LOW

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

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 36 distinct pattern matches across 2 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.

Hyper-Verbose Identifiers29 hits · 30 pts

Severity	File	Line	Snippet	Context
LOW	tests/CacheTest.php	26	public function testCacheKeyDifferentInputs(): void	CODE
LOW	tests/CacheTest.php	56	public function testCacheKeyOptionOrdering(): void	CODE
LOW	tests/CacheTest.php	109	public function testGetCachedStatsNotFound(): void	CODE
LOW	tests/CacheTest.php	118	public function testSetCachedStatsWithEmptyStats(): void	CODE
LOW	tests/CacheTest.php	150	public function testClearUserCacheNonExistent(): void	CODE
LOW	tests/TranslationsTest.php	48	public function testLocalesSortedAlphabetically(): void	CODE
LOW	tests/OptionsTest.php	50	public function testThemesInDocumentation(): void	CODE
LOW	tests/OptionsTest.php	66	public function testFallbackToDefaultTheme(): void	CODE
LOW	tests/OptionsTest.php	81	public function testThemesHaveValidParameters(): void	CODE
LOW	tests/OptionsTest.php	127	public function testColorOverrideParameters(): void	CODE
LOW⚡	tests/OptionsTest.php	223	public function testDateFormatDifferentYear(): void	CODE
LOW⚡	tests/OptionsTest.php	232	public function testDateFormatNoBracketsDiffYear(): void	CODE
LOW⚡	tests/OptionsTest.php	241	public function testDateFormatNoBracketsSameYear(): void	CODE
LOW	tests/OptionsTest.php	262	public function testAllThemeNamesNormalized(): void	CODE
LOW	tests/RenderTest.php	99	public function testLocaleRenderDateFormat(): void	CODE
LOW	tests/RenderTest.php	133	public function testBorderRadiusCannotInjectMarkup(): void	CODE
LOW	tests/RenderTest.php	153	public function testErrorMessageCannotInjectMarkup(): void	CODE
LOW	tests/RenderTest.php	166	public function testExcludedDaysCannotInjectMarkup(): void	CODE
LOW	tests/RenderTest.php	178	public function testRequestOptionsCannotInjectMarkup(): void	CODE
LOW	tests/RenderTest.php	360	public function testFirstAndThirdColumnsSwappedWhenDirectionIsRtl(): void	CODE
LOW	tests/StatsTest.php	99	public function testValidUsernameWithWhitelist(): void	CODE
LOW	tests/StatsTest.php	114	public function testNotWhitelistedUsername(): void	CODE
LOW	tests/StatsTest.php	326	public function testContributionDatesWithTimezone(): void	CODE
LOW	tests/StatsTest.php	409	public function testWeeklyStatsMissingWeek(): void	CODE
LOW	tests/StatsTest.php	453	public function testWeeklyStatsMissingThisWeek(): void	CODE
LOW	tests/StatsTest.php	522	public function testExcludeDaysNoContributionBeforeWeekend(): void	CODE
LOW	src/stats.php	14	function buildContributionGraphQuery(string $user, int $year): string	CODE
LOW	src/stats.php	43	function executeContributionGraphRequests(string $user, array $years): array	CODE
LOW	src/stats.php	420	function getWeeklyContributionStats(array $contributions): array	CODE

Structural Annotation Overuse7 hits · 10 pts

Severity	File	Line	Snippet	Context
LOW	CONTRIBUTING.md	105	### Step 0 : Find an issue	COMMENT
LOW	CONTRIBUTING.md	111	### Step 1 : Fork the Project	COMMENT
LOW	CONTRIBUTING.md	132	### Step 2 : Branch	COMMENT
LOW	CONTRIBUTING.md	141	### Step 3 : Work on the issue assigned	COMMENT
LOW	CONTRIBUTING.md	155	### Step 4 : Commit	COMMENT
LOW	CONTRIBUTING.md	164	### Step 5 : Work Remotely	COMMENT
LOW	CONTRIBUTING.md	178	### Step 6 : Pull Request	COMMENT