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

xiayansummer/fa-agent

https://github.com/xiayansummer/fa-agent · scanned 2026-06-16 01:02 UTC (2 months, 1 week ago)

110 raw signals (0 security + 110 graph)

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

Complete repo analysis

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

JSON
Combined
66.1
/100
Security checks
66
0 findings
System graph
66
100.0% cov · 92 findings
Critical
1
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 1 High 21 Medium 4 Low 62 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 92 Crowd 0 Layer: Software 11 Hardware 3 Security 22 Cicd 1 Quality 12 Api 43
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 66.1/100 with 100.0% coverage. It contains 889 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 110 findings — concentrated in api (43), software (27), security (22). Risk profile is high: 1 critical, 21 high, 4 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 88 of 92 actionable findings. 110 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.

critical System graph security Secrets conf 1.00 Possible secret in scripts/deploy_mvp.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/deploy_mvp.sh:9
high System graph security auth conf 1.00 FastAPI DELETE `delete_interaction` without auth dependency — backend/api/interactions.py:68
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/interactions.py:68 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_investor` without auth dependency — backend/api/investors.py:744
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/investors.py:744 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_outreach` without auth dependency — backend/api/outreach.py:59
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/outreach.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_schedule_event` without auth dependency — backend/api/calendar.py:618
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/calendar.py:618 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bind_phone` without auth dependency — backend/auth/router.py:69
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/auth/router.py:69 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_interaction` without auth dependency — backend/api/interactions.py:35
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/interactions.py:35 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_investor` without auth dependency — backend/api/investors.py:490
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/investors.py:490 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_schedule_event` without auth dependency — backend/api/calendar.py:550
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/calendar.py:550 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dismiss_event` without auth dependency — backend/api/calendar.py:463
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/calendar.py:463 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `free_chat` without auth dependency — backend/api/agent.py:375
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent.py:375 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_upload_token` without auth dependency — backend/api/upload.py:32
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/upload.py:32 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `report_subscribe_grant` without auth dependency — backend/api/me.py:147
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/me.py:147 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_workflow` without auth dependency — backend/api/agent.py:160
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent.py:160 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_review` without auth dependency — backend/api/agent.py:243
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent.py:243 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_tencent_token` without auth dependency — backend/api/me.py:115
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/me.py:115 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_business_card` without auth dependency — backend/api/investors.py:402
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/investors.py:402 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `wechat_login` without auth dependency — backend/auth/router.py:42
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/auth/router.py:42 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `configure_tencent` without auth dependency — backend/api/me.py:92
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/me.py:92 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_investor` without auth dependency — backend/api/investors.py:611
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/investors.py:611 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_me` without auth dependency — backend/api/me.py:53
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/me.py:53 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_schedule_event` without auth dependency — backend/api/calendar.py:582
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/calendar.py:582 securityAuth fastapi unauth mutation
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
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
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 14 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker.m.daocloud.io/library/python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/skills/qmingpian.py:qmingpian_search_person_by_phone, backend/skills/qmingpian.py:qmingpian_search_person This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docume…
3 occurrences
repo-level (3 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: dispatch_outreach_impl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/dispatch_outreach.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
alembic/env.py:45
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
alembic/versions/2b56329d65d3_initial_schema.py:120
alembic/versions/30cc917a9faf_investors_add_qmingpian_person_id.py:31
alembic/versions/4a8b7c2e1d5f_investors_add_avatar_card.py:25
alembic/versions/5b9c8d4e3f7a_add_familiarity_qmingpian_username.py:27
alembic/versions/6e30809e653d_mvp_schema_phone_unique_token_.py:31
alembic/versions/9f1c8a2d4e6b_ir_investor_membership.py:51
alembic/versions/a1b2c3d4e5f6_calendar_events.py:41
alembic/versions/b2c3d4e5f6a7_wx_schedule_reminders.py:35
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_candidates_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/workflows/smart_list.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: rank_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/workflows/smart_list.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/auth/jwt.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: review_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/nodes/review_node.py:5
low System graph software Dead code conf 1.00 Possibly dead Python function: run_daily_push_for_all_irs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/scheduled.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: run_milestone_outreach_for_all_irs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/scheduled.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: run_schedule_reminders
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agent/scheduled.py:134
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
alembic/versions/2b56329d65d3_initial_schema.py:21
alembic/versions/30cc917a9faf_investors_add_qmingpian_person_id.py:21
alembic/versions/4a8b7c2e1d5f_investors_add_avatar_card.py:20
alembic/versions/5b9c8d4e3f7a_add_familiarity_qmingpian_username.py:20
alembic/versions/6e30809e653d_mvp_schema_phone_unique_token_.py:21
alembic/versions/9f1c8a2d4e6b_ir_investor_membership.py:20
alembic/versions/a1b2c3d4e5f6_calendar_events.py:20
alembic/versions/b2c3d4e5f6a7_wx_schedule_reminders.py:20
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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: DELETE /events/{event_id}
`backend/api/calendar.py` declares `DELETE /events/{event_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: DELETE /{investor_id}
`backend/api/investors.py` declares `DELETE /{investor_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: DELETE /{investor_id}/interactions/{interaction_id}
`backend/api/interactions.py` declares `DELETE /{investor_id}/interactions/{interaction_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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{record_id}
`backend/api/outreach.py` declares `DELETE /{record_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 /
`backend/api/investors.py` declares `GET /` 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 /daily
`backend/api/calendar.py` declares `GET /daily` 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 /events/{event_id}
`backend/api/calendar.py` declares `GET /events/{event_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 /history
`backend/api/outreach.py` declares `GET /history` 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 /month
`backend/api/calendar.py` declares `GET /month` 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 /pending
`backend/api/outreach.py` declares `GET /pending` 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 /qmingpian/by-name
`backend/api/investors.py` declares `GET /qmingpian/by-name` 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 /qmingpian/searchhit
`backend/api/investors.py` declares `GET /qmingpian/searchhit` 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 /search
`backend/api/investors.py` declares `GET /search` 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 /sign
`backend/api/upload.py` declares `GET /sign` 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 /tencent/meetings
`backend/api/me.py` declares `GET /tencent/meetings` 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 /tencent/meetings/{meeting_id}/records
`backend/api/me.py` declares `GET /tencent/meetings/{meeting_id}/records` 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 /{investor_id}
`backend/api/investors.py` declares `GET /{investor_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 /{investor_id}/interactions
`backend/api/interactions.py` declares `GET /{investor_id}/interactions` 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 /{thread_id}/state
`backend/api/agent.py` declares `GET /{thread_id}/state` 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: PATCH /users/{user_id}
`backend/api/admin.py` declares `PATCH /users/{user_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: POST /
`backend/api/investors.py` declares `POST /` 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/calendar/dismiss
`miniprogram/pages/calendar-day/index.ts` declares `POST /api/calendar/dismiss` 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/calendar/events
`miniprogram/pages/schedule-edit/index.ts` declares `POST /api/calendar/events` 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/me/subscribe
`miniprogram/utils/subscribe.ts` declares `POST /api/me/subscribe` 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 /bind_phone
`backend/auth/router.py` declares `POST /bind_phone` 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 /chat
`backend/api/agent.py` declares `POST /chat` 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 /dismiss
`backend/api/calendar.py` declares `POST /dismiss` 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 /events
`backend/api/calendar.py` declares `POST /events` 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 /login
`backend/auth/router.py` declares `POST /login` 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 /run
`backend/api/agent.py` declares `POST /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 api Wiring conf 1.00 Unused endpoint: POST /subscribe
`backend/api/me.py` declares `POST /subscribe` 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 /tencent/test
`backend/api/me.py` declares `POST /tencent/test` 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 /token
`backend/api/upload.py` declares `POST /token` 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 /upload-business-card
`backend/api/investors.py` declares `POST /upload-business-card` 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 /users
`backend/api/admin.py` declares `POST /users` 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 /{investor_id}/interactions
`backend/api/interactions.py` declares `POST /{investor_id}/interactions` 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 /{thread_id}/review
`backend/api/agent.py` declares `POST /{thread_id}/review` 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: PUT /
`backend/api/me.py` declares `PUT /` 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: PUT /api/me
`miniprogram/pages/me/index.ts` declares `PUT /api/me` 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: PUT /api/me/tencent
`miniprogram/pages/tencent-setup/index.ts` declares `PUT /api/me/tencent` 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: PUT /events/{event_id}
`backend/api/calendar.py` declares `PUT /events/{event_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: PUT /tencent
`backend/api/me.py` declares `PUT /tencent` 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: PUT /{investor_id}
`backend/api/investors.py` declares `PUT /{investor_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 quality Complexity conf 1.00 Very large file: backend/agent/orchestrator_tools/direct.py (1252 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/66101f18-f72b-4c3d-98f2-e8032bc5c446/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/66101f18-f72b-4c3d-98f2-e8032bc5c446/

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.