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.
242 of your 411 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 113.84s for a 145.7 MB repo slow.
  • Repobility's analysis ran in 14.61s after the clone landed.

PaddlePaddle/PaddleOCR

https://github.com/PaddlePaddle/PaddleOCR · scanned 2026-06-04 23:21 UTC (15 hours, 21 minutes ago) · 10 languages

1202 findings (366 legacy + 836 scanner) 11/13 scanners ran 54th percentile · Python · large (100-500K LoC) Scanner says 69 (higher by 6)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 15 hours, 20 minutes ago · v4 · 575 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
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 66.0 0.20 13.20
documentation_score 70.0 0.15 10.50
practices_score 74.0 0.15 11.10
code_quality 63.0 0.10 6.30
Overall 1.00 75.1
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/amd-gpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#2
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/nvidia-gpu-sm120/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#3
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/metax-gpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#4
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/huawei-npu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#5
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/iluvatar-gpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#6
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/intel-gpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#7
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/kunlunxin-xpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#8
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/nvidia-gpu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#9
.env file present in repo: deploy/paddleocr_vl_docker/accelerators/hygon-dcu/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#10
FastAPI POST `_handle_infer` without auth dependency — deploy/paddleocr_vl_docker/hps/gateway/app.py:327
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in deploy/paddleocr_vl_docker/hps/gateway/app.py:327.
deploy/paddleocr_vl_docker/hps/gateway/app.py:327

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/3dad2478-306d-4d44-a628-9cd6ca4ce6f2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3dad2478-306d-4d44-a628-9cd6ca4ce6f2/

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.