PaddlePaddle/FastDeploy

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.

Scan timing: clone 10.23s · analysis 39.56s · 31.8 MB · GitHub API rate-limit (preflight)

https://github.com/PaddlePaddle/FastDeploy · scanned 2026-05-31 01:23 UTC (5 days, 14 hours ago) · 10 languages

1206 findings (392 legacy + 814 scanner) 11/13 scanners ran 82nd percentile · Python · large (100-500K LoC) Scanner says 69 (higher by 16)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · 809 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

100.0% cov · 417 gaps

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	83.0	0.15	12.45
`practices_score`	92.0	0.15	13.80
`code_quality`	45.0	0.10	4.50
Overall		1.00	84.8

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 10 High 270 Medium 91 Low 330 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 392 9-layer 417 Crowd 0 Layer: Software 125 Quality 532 Security 70 Cicd 55 Hardware 1 Frontend 1 Api 25

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 69.3/100 with 100.0% coverage. It contains 17404 nodes across 29 cross-layer flows, written primarily in mixed languages. Engine surfaced 417 findings — concentrated in quality (270), software (53), security (39). Risk profile is high: 1 critical, 31 high, 25 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 25 of 809 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low 9-layer api wiring conf 1.00 Unused endpoint: GET /clear_load_weight

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /clear_load_weight` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /config-info

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /config-info` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /decode_instances

`fastdeploy/router/router.py` declares `GET /decode_instances` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /load

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /load` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /registered_number

`fastdeploy/router/router.py` declares `GET /registered_number` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /update_model_weight

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /update_model_weight` 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 …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /v1/is_paused

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /v1/is_paused` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /v1/models

`fastdeploy/entrypoints/openai/api_server.py` declares `GET /v1/models` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /check_redundant

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /check_redundant` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /controller/reset_scheduler

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /controller/reset_scheduler` 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 c…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /controller/scheduler

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /controller/scheduler` 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 consume…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /generate

`fastdeploy/entrypoints/api_server.py` declares `POST /generate` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /get_per_expert_tokens_stats

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /get_per_expert_tokens_stats` 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 …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /rearrange_experts

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /rearrange_experts` 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 i…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /register

`fastdeploy/router/router.py` declares `POST /register` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/abort_requests

`fastdeploy/router/router.py` declares `POST /v1/abort_requests` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/chat/completions

`fastdeploy/router/router.py` declares `POST /v1/chat/completions` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/completions

`fastdeploy/router/router.py` declares `POST /v1/completions` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/embeddings

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/embeddings` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/pause

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/pause` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/resume

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/resume` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/reward

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/reward` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/sleep

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/sleep` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/update_weights

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/update_weights` 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 i…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /v1/wakeup

`fastdeploy/entrypoints/openai/api_server.py` declares `POST /v1/wakeup` 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.

wiringunused-endpoint

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/ab654ff4-2d45-41c2-a338-f39e691f30b3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ab654ff4-2d45-41c2-a338-f39e691f30b3/

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.