AI Slop Code Risk Monitor

cp-algorithms/cp-algorithms

Name: cp-algorithms/cp-algorithms — C++ 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).

Algorithm and data structure articles for https://cp-algorithms.com (based on http://e-maxx.ru)

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cp-algorithms/cp-algorithms, a C++ project with 11,482 GitHub stars. SynthScan examined 39,298 lines of code across 278 source files, recording 30 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.0 (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.

1.0

Adjusted Signal

1.0

Raw Pattern Score

100%

Time Factor

2026-10-26

Last Push

11.5K

Stars

C++

Language

39.3K

Lines of Code

278

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

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

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

PR Review Velocity Impact 3.8/100 · LOW

Which changes need focused human review? 30 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 30

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 30 distinct pattern matches across 3 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 Identifiers20 hits · 26 pts

Severity	File	Line	Snippet	Context
LOW	scripts/test_article_previews.py	61	def test_changed_articles_links_assets_and_noindex(self):	CODE
LOW⚡	scripts/test_article_previews.py	85	def test_asset_bundle_is_shared_and_ignores_feed_timestamps(self):	CODE
LOW⚡	scripts/test_article_previews.py	95	def test_asset_changes_get_a_distinct_bundle(self):	CODE
LOW⚡	scripts/test_article_previews.py	102	def test_project_site_keeps_main_and_pr_links_on_preview_host(self):	CODE
LOW	scripts/test_article_previews.py	123	def test_rejects_trusted_origins_before_changing_publication(self):	CODE
LOW	scripts/test_article_previews.py	137	def test_navigation_only_change_previews_just_the_home_page(self):	CODE
LOW	scripts/test_article_previews.py	153	def test_new_article_with_navigation_stays_small_and_readme_adds_only_home(self):	CODE
LOW	scripts/test_article_previews.py	167	def test_readme_links_to_new_articles_stay_in_the_preview(self):	CODE
LOW	scripts/test_article_previews.py	177	def test_review_index_links_changed_pages_main_and_source_revision(self):	CODE
LOW⚡	scripts/test_article_previews.py	195	def test_shared_change_keeps_directly_edited_articles_first(self):	CODE
LOW⚡	scripts/test_article_previews.py	205	def test_contributing_symlink_maps_to_rendered_contrib_page(self):	CODE
LOW⚡	scripts/test_article_previews.py	210	def test_no_article_change_creates_only_a_noindex_hub(self):	CODE
LOW⚡	scripts/test_article_previews.py	220	def test_new_article_does_not_offer_a_missing_main_page(self):	CODE
LOW⚡	scripts/test_article_previews.py	226	def test_update_removes_old_pages_and_cleanup_keeps_shared_assets(self):	CODE
LOW	scripts/test_article_previews.py	242	def test_main_preview_shares_assets_and_survives_pr_cleanup(self):	CODE
LOW⚡	scripts/test_article_previews.py	266	def test_remote_pr_requires_main_preview(self):	CODE
LOW⚡	scripts/test_article_previews.py	271	def test_legacy_pr_landing_links_to_review_pages(self):	CODE
LOW⚡	scripts/test_article_previews.py	280	def test_cleanup_removes_legacy_preview(self):	CODE
LOW⚡	scripts/test_article_previews.py	287	def test_invalid_build_does_not_replace_previous_preview(self):	CODE
LOW⚡	scripts/test_article_previews.py	295	def test_rejects_symlinks_overlapping_roots_and_unsafe_article_paths(self):	CODE

Structural Annotation Overuse6 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	src/others/tortoise_and_hare.md	23	### Step 1: Presence of the cycle	COMMENT
LOW	src/others/tortoise_and_hare.md	37	### Step 2: Starting point of the cycle	COMMENT
LOW	src/others/tortoise_and_hare.md	73	### Step 1: Presence of the cycle	COMMENT
LOW	src/others/tortoise_and_hare.md	84	### Step 2: Starting point of the cycle	COMMENT
LOW	src/dynamic_programming/zero_matrix.md	15	### Step 1: Auxiliary dynamic	COMMENT
LOW	src/dynamic_programming/zero_matrix.md	31	### Step 2: Problem solving	COMMENT

Deep Nesting4 hits · 4 pts

Severity	File	Line	Context
LOW	test/extract_snippets.py	11	CODE
LOW	scripts/article_previews.py	120	CODE
LOW	scripts/article_previews.py	214	CODE
LOW	scripts/test_preview_deployment.py	61	CODE