Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo
95 of your 167 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 19.61s · analysis 3.31s · 25.2 MB · GitHub API rate-limit (preflight)

NanmiCoder/MediaCrawler

https://github.com/NanmiCoder/MediaCrawler · scanned 2026-06-05 11:42 UTC (5 days, 11 hours ago) · 10 languages

365 raw signals (159 security + 206 graph) 11/13 scanners ran 74th percentile · Python · medium (20-100K LoC) System graph score 60 (higher by 17)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 11 hours ago · v2 · 139 actionable findings from 2 signal sources. 123 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
72.1
/100
Security checks
84
57 findings
System graph
60
100.0% cov · 82 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 100.0 0.25 25.00
testing_score 63.0 0.20 12.60
documentation_score 72.0 0.15 10.80
practices_score 71.0 0.15 10.65
code_quality 71.0 0.10 7.10
Overall 1.00 77.4
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 27 Medium 8 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 57 System graph 82 Crowd 0 Layer: Software 37 Quality 60 Security 15 Cicd 2 Frontend 2 Api 23

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 4 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
4 matching findings on this repo
  • low Near-duplicate function bodies in 4 places
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 7 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 6 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
6 matching findings on this repo
  • info Commented-code block (5 lines) in media_platform/zhihu/client.py:254
  • info Commented-code block (5 lines) in media_platform/zhihu/core.py:290
  • info Commented-code block (5 lines) in config/base_config.py:78
  • info Commented-code block (7 lines) in config/dy_config.py:23
  • info Commented-code block (5 lines) in proxy/base_proxy.py:21
  • info Commented-code block (6 lines) in tools/slider_util.py:115
View all commented-out code findings →
Config drift 16 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
12 matching findings on this repo
  • high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:27
  • low File has no detected symbols: config/zhihu_config.py
  • low File has no detected symbols: config/base_config.py
  • low File has no detected symbols: config/tieba_config.py
  • low File has no detected symbols: config/dy_config.py
  • low File has no detected symbols: config/ks_config.py
  • low File has no detected symbols: config/db_config.py
  • low File has no detected symbols: config/bilibili_config.py
  • low File has no detected symbols: config/xhs_config.py
  • low File has no detected symbols: config/weibo_config.py
  • info Commented-code block (5 lines) in config/base_config.py:78
  • info Commented-code block (7 lines) in config/dy_config.py:23
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/0d236f0c-360d-4752-8c2f-e650610910e6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0d236f0c-360d-4752-8c2f-e650610910e6/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.