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
136 of your 243 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 97.71s for a 147.9 MB repo slow.
  • Repobility's analysis ran in 23.54s after the clone landed.

nexu-io/open-design

https://github.com/nexu-io/open-design · scanned 2026-06-05 09:50 UTC (5 days, 17 hours ago) · 10 languages

2828 raw signals (212 security + 2616 graph) 11/13 scanners ran 49th percentile · Typescript · huge (>500K LoC) System graph score 60 (higher by 25)

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

Complete repo analysis

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

JSON
Combined
70.7
/100
Security checks
82
98 findings
System graph
60
100.0% cov · 1134 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 95.0 0.20 19.00
documentation_score 100.0 0.15 15.00
practices_score 81.0 0.15 12.15
code_quality 45.0 0.10 4.50
Overall 1.00 84.7
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 111 Medium 77 Low 383 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 98 System graph 1134 Crowd 0 Layer: Quality 917 Cicd 11 Software 85 Security 17 Frontend 86 Network 2 Api 114

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 6 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.
6 matching findings on this repo
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 5 places
  • low Near-duplicate function bodies in 9 places
  • low Near-duplicate function bodies in 6 places
View all duplicates & near-duplicates findings →
Legacy markers 24 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.
12 matching findings on this repo
  • low Stray `console.log` in TS/JS — apps/daemon/src/legacy-data-migrator.ts:306
  • low Old/deprecated-named symbol `nLegacy` in apps/daemon/tests/design-systems.test.…
  • low Old/deprecated-named symbol `nLegacy` in apps/daemon/tests/tools-connectors-cli…
  • info Commented-code block (7 lines) in apps/daemon/tests/legacy-data-migrator.test.t…
  • info Commented-code block (5 lines) in apps/daemon/src/legacy-data-migrator.ts:241
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/types.t…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
  • low Old/deprecated-named symbol `artifactKickerLegacy` in apps/web/src/i18n/locales…
View all legacy markers findings →
Commented-out code 615 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 (7 lines) in apps/landing-page/astro.config.ts:23
  • info Commented-code block (16 lines) in apps/landing-page/scripts/copy-example-html.…
  • info Commented-code block (5 lines) in apps/landing-page/scripts/generate-previews.t…
  • info Commented-code block (6 lines) in apps/landing-page/app/content.config.ts:102
  • info Commented-code block (6 lines) in apps/landing-page/app/page.tsx:107
  • info Commented-code block (6 lines) in apps/landing-page/app/content-i18n.ts:684
  • info Commented-code block (5 lines) in apps/landing-page/app/_lib/catalog.ts:38
  • info Commented-code block (6 lines) in apps/landing-page/app/_lib/bundled-plugins.ts…
  • info Commented-code block (7 lines) in apps/landing-page/app/_lib/plugin-facets.ts:9
  • info Commented-code block (8 lines) in apps/landing-page/app/_lib/plugin-slug.ts:3
  • info Commented-code block (5 lines) in apps/desktop/tests/main/hide-window-exiting-f…
  • info Commented-code block (6 lines) in apps/desktop/tests/main/save-print-ready-docu…
View all commented-out code findings →
Config drift 22 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.
12 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… apps/web/src/edit-mode/source-patches.ts:119
  • low Possibly dead Python function: cmd_config design-templates/last30days/scripts/watchlist.py:…
  • low Possibly dead Python function: config_exists design-templates/last30days/scripts/lib/env.py:366
  • low File has no detected symbols: apps/landing-page/astro.config.ts
  • low File has no detected symbols: apps/landing-page/app/content.config.ts
  • low File has no detected symbols: apps/telemetry-worker/vitest.config.ts
  • low File has no detected symbols: apps/desktop/vitest.config.ts
  • low File has no detected symbols: apps/daemon/vitest.config.ts
  • low Very large file: apps/daemon/src/mcp-config.ts (1170 lines)
  • info Commented-code block (7 lines) in apps/landing-page/astro.config.ts:23
  • info Commented-code block (6 lines) in apps/landing-page/app/content.config.ts:102
  • info Commented-code block (6 lines) in apps/daemon/tests/app-config.test.ts:19
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/4f01aef0-39c8-44fa-a798-a497d4fe9632/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4f01aef0-39c8-44fa-a798-a497d4fe9632/

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.