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.

earthtojake/text-to-cad

https://github.com/earthtojake/text-to-cad · scanned 2026-07-23 19:38 UTC (4 days, 17 hours ago)

263 raw signals (0 security + 263 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v3 · last Δ +2.0 (diff) · 259 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

90.0% cov · 259 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 23 Medium 108 Low 110 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 259 Crowd 0 Layer: Software 27 Frontend 20 Security 96 Quality 80 Cicd 2 Dependencies 32 Api 2

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 3 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 8 places

View all duplicates & near-duplicates findings →

Legacy markers 3 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

3 matching findings on this repo

low Old/deprecated-named symbol `final_joint_values_legacy` in viewer/moveit2_serve…
low Old/deprecated-named symbol `final_joint_values_legacy` in skills/cad-viewer/sc…
low Old/deprecated-named symbol `final_joint_values_legacy` in plugins/cad/skills/c…

View all legacy markers 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/41745799-8d92-4609-af4e-6f47a601b418/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/41745799-8d92-4609-af4e-6f47a601b418/

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.