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
142 of your 195 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 37.1s for a 51.0 MB repo slow.
  • Repobility's analysis ran in 16.47s after the clone landed.

rapidsai/cuml

https://github.com/rapidsai/cuml · scanned 2026-06-05 22:09 UTC (4 days, 10 hours ago) · 10 languages

507 raw signals (187 security + 320 graph) 11/13 scanners ran 72nd percentile · Python · large (100-500K LoC)

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

Complete repo analysis

Last scanned 4 days, 10 hours ago · v2 · 162 actionable findings from 2 signal sources. 175 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
82.1
/100
Security checks
81
69 findings
System graph
83
77.8% cov · 93 findings
Critical
0
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 97.0 0.20 19.40
documentation_score 97.0 0.15 14.55
practices_score 68.0 0.15 10.20
code_quality 46.0 0.10 4.60
Overall 1.00 82.8
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 0 High 11 Medium 11 Low 57 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 69 System graph 93 Crowd 0 Layer: Quality 109 Cicd 6 Security 10 Software 33 Api 1 Hardware 2 Frontend 1
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": 1315, "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": 1315, "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/b3d066e7-1cde-4e03-96f1-1c60f8282b9d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b3d066e7-1cde-4e03-96f1-1c60f8282b9d/

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.