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

yangyuxin-hub/AI-Competitive-Radar

https://github.com/yangyuxin-hub/AI-Competitive-Radar · scanned 2026-06-16 01:04 UTC (2 months, 1 week ago)

57 raw signals (0 security + 57 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 51 actionable findings from 1 signal source. 6 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
69.3
/100
Security checks
69
0 findings
System graph
69
77.8% cov · 51 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 4 Medium 9 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 51 Crowd 0 Layer: Software 10 Frontend 4 Security 5 Cicd 1 Quality 22 Api 9
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 69.3/100 with 77.8% coverage. It contains 1300 nodes across 12 cross-layer flows, written primarily in mixed languages. Engine surfaced 57 findings — concentrated in quality (28), software (10), api (9). Risk profile is high: 0 critical, 4 high, 9 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 43 of 51 actionable findings. 57 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security auth conf 1.00 FastAPI POST `api_intake_stream` without auth dependency — api/main.py:193
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/main.py:193 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_propose` without auth dependency — api/main.py:180
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/main.py:180 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_questions` without auth dependency — api/main.py:186
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/main.py:186 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_run` without auth dependency — api/main.py:708
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/main.py:708 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — web/lib/api.ts:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.local.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.local.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 20 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 86 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANALYZER_DERIV_MAX_PER_TYPE`, `ANALYZER_DERIV_SNIPPET_LEN`, `ANALYZER_DERIV_TIMEOUT`, `ANALYZER_FACTS_TIMEOUT`, `ANALYZER_FEATURE_ENRICH`, `ANALYZER_FEATURE_TREE_SPLIT`, `ANALYZER_GAP_MAX_QUERIES`, `ANALYZER_GAP_MAX_ROUNDS` + 78 more. Add them (wi…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 354 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api/main.py:api_reports, api/main.py:api_report This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: src/collector_adapters.py:fetch, src/collector_adapters.py:fetch, src/collector_adapters.py:fetch, src/collector_adapters.py:fetch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: check_aggregation_integrity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/reviewer.py:123
low System graph software Dead code conf 1.00 Possibly dead Python function: check_claim_type_compatibility
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/reviewer.py:104
low System graph software Dead code conf 1.00 Possibly dead Python function: check_evidence_reference_integrity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/reviewer.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: check_freshness_and_confidence
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/reviewer.py:220
low System graph software Dead code conf 1.00 Possibly dead Python function: discover_urls
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/collector_common.py:141
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/collector_adapters.py:591
low System graph software Dead code conf 1.00 Possibly dead Python function: planned_claim_types_for_meta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evidence_plan.py:162
low System graph software Dead code conf 1.00 Possibly dead Python function: register
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/skill.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: reviewer_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/reviewer.py:807
low System graph software Dead code conf 1.00 Possibly dead Python function: worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/main.py:557
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — web/components/AnalyzeFlow.tsx:726
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/checklist
`api/main.py` declares `GET /api/checklist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/reports
`api/main.py` declares `GET /api/reports` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/reports/{report_id}
`api/main.py` declares `GET /api/reports/{report_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stage_quality
`api/main.py` declares `GET /api/stage_quality` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/timeline
`api/main.py` declares `GET /api/timeline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/intake/propose
`api/main.py` declares `POST /api/intake/propose` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/intake/questions
`api/main.py` declares `POST /api/intake/questions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/intake/stream
`api/main.py` declares `POST /api/intake/stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/run
`api/main.py` declares `POST /api/run` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/analyzer.py (1107 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/components/AnalyzeFlow.tsx (1319 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/components/ReportView.tsx (1290 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/e4c1fbb6-3d82-43fb-9acf-fd95de2b394e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e4c1fbb6-3d82-43fb-9acf-fd95de2b394e/

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.