rapidsai/cuml

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.

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.

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

77.8% cov · 93 findings

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 30 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in python/libcuml/tests/test_libcuml_linkage.py:…
info Commented-code block (5 lines) in python/cuml/tests/test_umap.py:436
info Commented-code block (9 lines) in python/cuml/tests/test_no_cuinit.py:45
info Commented-code block (7 lines) in python/cuml/tests/test_lars.py:218
info Commented-code block (5 lines) in python/cuml/tests/test_kernel_density.py:176
info Commented-code block (5 lines) in python/cuml/tests/test_base.py:55
info Commented-code block (55 lines) in python/cuml/tests/test_qn.py:199
info Commented-code block (7 lines) in python/cuml/tests/test_dbscan.py:335
info Commented-code block (6 lines) in python/cuml/tests/explainer/test_explainer_ke…
info Commented-code block (11 lines) in python/cuml/cuml/tsa/batched_lbfgs.py:205
info Commented-code block (5 lines) in python/cuml/cuml/dask/neighbors/nearest_neigh…
info Commented-code block (5 lines) in python/cuml/cuml/testing/utils.py:152

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:6

View all config drift findings →

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.