AI Slop Code Risk Monitor

1c7/chinese-independent-developer

SlopCodeMonitor badge for 1c7/chinese-independent-developer Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

👩🏿‍💻👨🏾‍💻👩🏼‍💻👨🏽‍💻👩🏻‍💻中国独立开发者项目列表 -- 分享大家都在做什么

1.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for 1c7/chinese-independent-developer with 61,972 GitHub stars. SynthScan examined 13,296 lines of code across 21 source files, recording 12 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 1.9 (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.9
Adjusted Signal
1.9
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
62.0K
Stars
—
Language
13.3K
Lines of Code
21
Files
12
Pattern Hits
2026-10-31
Scan Date
0.10
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 6.2/100 · LOW

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

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

PR Review Velocity Impact 8.6/100 · LOW

Which changes need focused human review? 12 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 2MEDIUM 1LOW 9

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 12 distinct pattern matches across 5 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 Identifiers7 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡.github/tests/test_collect_traffic.py19 def test_overlap_replaces_counts_and_keeps_older_history(self):CODE
LOW⚡.github/tests/test_collect_traffic.py28 def test_manual_reruns_keep_history_and_one_snapshot_per_day(self):CODE
LOW⚡.github/tests/test_collect_traffic.py38 def test_endpoint_failure_does_not_overwrite_archive(self):CODE
LOW⚡.github/tests/test_process_item.py76 def test_contributor_success_reaction_does_not_suppress_submission(self):CODE
LOW⚡.github/tests/test_process_item.py84 def test_admin_success_reaction_marks_submission_complete(self):CODE
LOW⚡.github/tests/test_process_item.py92 def test_scanner_skips_pull_requests(self):CODE
LOW.github/tests/test_process_item.py106 def test_scanner_keeps_admin_marked_issues(self):CODE
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGH…aude/skills/chinese-indie-dev/references/precedents.md157- **155 条漏清(2026-06-23 ~ 07-28)**:#160 里 70 条、各 issue/PR 上 85 条致谢评论带着「Generated by Claude Code」,横跨 `1c7` 和 `claude[bot]`CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGH.github/scripts/process_item.py225except:CODE
Decorative Section Separators1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/scripts/process_item.py18# ==========================================COMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOW.github/scripts/pending_submissions.py77CODE
LOW.github/scripts/process_item.py128CODE