The-AI-Alliance/cube-standard

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.

94 of your 246 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.09s · analysis 7.24s · 5.6 MB · GitHub preflight 476ms

https://github.com/The-AI-Alliance/cube-standard · scanned 2026-06-05 18:25 UTC (4 days, 19 hours ago) · 10 languages

333 raw signals (167 security + 166 graph) 59th percentile · Python · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 63 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	48.2	0.25	12.05
`testing_score`	87.0	0.20	17.40
`documentation_score`	81.0	0.15	12.15
`practices_score`	70.0	0.15	10.50
`code_quality`	34.5	0.10	3.45
Overall		1.00	68.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 33 Medium 23 Low 41 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 92 System graph 63 Crowd 0 Layer: Quality 89 Security 8 Software 49 Frontend 2 Network 2 Cicd 4 Api 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 2 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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 15 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 cube-tools/cube-browser-tool/tests/test_bgym_…
info Commented-code block (6 lines) in cube-resources/cube-infra-azure/src/cube_infr…
info Commented-code block (5 lines) in cube-resources/cube-infra-toolkit/src/cube_in…
info Commented-code block (7 lines) in cube-resources/cube-infra-aws/src/cube_infra_…
info Commented-code block (9 lines) in cube-resources/cube-infra-daytona/src/cube_in…
info Commented-code block (5 lines) in src/cube/infra_utils.py:24
info Commented-code block (5 lines) in src/cube/tool.py:268
info Commented-code block (5 lines) in src/cube/cli.py:1269
info Commented-code block (5 lines) in src/cube/server.py:120
info Commented-code block (11 lines) in src/cube/benchmark.py:403
info Commented-code block (7 lines) in src/cube/task.py:44
info Commented-code block (6 lines) in src/cube/integrations/nemogym.py:167

View all commented-out code findings →

Config drift 3 findings

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.

3 matching findings on this repo

high Phantom test coverage: test_spawn_rejects_config_without_sub_benchmark_tag tests/test_benchmark_composite.py:201
low File has no detected symbols: docs/_includes/mermaid_config.js
low Old/deprecated-named symbol `test_config_registry_lookup_returns_independent_de…

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/427d983d-a5bc-43ee-bedb-c5b68d62f339/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/427d983d-a5bc-43ee-bedb-c5b68d62f339/

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.