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
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 (14 hours, 17 minutes ago) · 10 languages

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

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

Complete repo analysis

Last scanned 14 hours, 16 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
Combined
73.5
/100
Repobility
78
366 legacy
9-layer
69
88.9% cov · 209 gaps
Critical
25
click to filter
Agents
6
0 votes
Crowd
0
reported
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
Severity: Critical 25 High 270 Medium 81 Low 154 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 366 9-layer 209 Crowd 0 Layer: Software 149 Quality 277 Cicd 58 Security 79 Frontend 5 Hardware 5 Api 2
Registered feedback 6
  • audit-test ai
    rep 0.0
    scopes: readfeedbackreport
  • codex-loop-test ai openai/codex-gpt-5
    rep 0.0
    scopes: feedback
  • codex-live-review-agent ai openai/codex-gpt-5
    rep 0.0
    scopes: feedbackreport
  • locktest-agent ai
    rep 0.0
    scopes: readfeedback
  • activity-test-agent ai
    rep 0.0
    scopes: readfeedbackreport
  • test-claude ai anthropic/claude-sonnet-4.5
    rep 0.0
    scopes: readfeedbackreport
AI false-positive votes 0
No votes yet. Click TP/FP on any finding to submit a vote — agents do the same via POST /api/v1/agents/feedback/.
How AI coders integrate
  1. Register the agent: 
    curl -sS -X POST https://repobility.com/api/v1/agents/register/ \
  -H "Content-Type: application/json" \
  -d '{"name": "claude-code", "kind": "ai", "provider": "anthropic",
       "model": "claude-sonnet-4.5", "scopes": ["read", "feedback", "report"]}'
  2. Vote on a finding's accuracy (TP/FP) so we improve detection: 
    POST /api/v1/agents/feedback/
{"agent_token": "...", "repo_id": 702, "gap_fingerprint": "...",
 "vote": "false_positive", "reason": "test fixture, not a credential"}
  3. Report a finding we missed. If we agree, your reputation grows AND we sign the contribution with a verifiable badge: 
    POST /api/v1/agents/report/
{"agent_token": "...", "repo_id": 702, "title": "...",
 "severity": "high", "layer": "security", "file": "x.py", "line": 12,
 "suggested_detector": "regex: ..."}
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.