hexclave/hexclave

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.

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

Scan timing: clone 22.04s · analysis 20.88s · 43.9 MB · GitHub API rate-limit (preflight)

https://github.com/hexclave/hexclave · scanned 2026-06-05 18:34 UTC (4 days, 18 hours ago) · 10 languages

1612 raw signals (156 security + 1456 graph) 10/13 scanners ran 65th percentile · Typescript · large (100-500K LoC) System graph score 57 (higher by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 723 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`	68.0	0.20	13.60
`documentation_score`	85.0	0.15	12.75
`practices_score`	74.0	0.15	11.10
`code_quality`	70.0	0.10	7.00
Overall		1.00	78.5

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 5 High 126 Medium 133 Low 251 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 82 System graph 723 Crowd 0 Layer: Quality 269 Security 46 Cicd 13 Software 55 Frontend 263 Network 25 Hardware 22 Api 112

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `getItemQuantityForCustomerLegacy` in apps/backend/…

View all legacy markers findings →

Commented-out code 104 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 apps/dashboard/src/components/hexclave-compan…
info Commented-code block (8 lines) in apps/dashboard/src/components/design-componen…
info Commented-code block (5 lines) in apps/dashboard/src/components/commands/create…
info Commented-code block (6 lines) in apps/dashboard/src/components/payments/checko…
info Commented-code block (5 lines) in apps/dashboard/src/components/vibe-coding/cod…
info Commented-code block (6 lines) in apps/dashboard/src/components/data-table/tran…
info Commented-code block (6 lines) in apps/dashboard/src/app/(main)/(protected)/lay…
info Commented-code block (5 lines) in apps/dashboard/src/app/(main)/(protected)/(ou…
info Commented-code block (7 lines) in apps/dashboard/src/app/(main)/(protected)/(ou…
info Commented-code block (5 lines) in apps/dashboard/src/app/(main)/(protected)/pro…
info Commented-code block (6 lines) in apps/dashboard/src/app/(main)/(protected)/pro…
info Commented-code block (5 lines) in apps/dashboard/src/app/(main)/(protected)/pro…

View all commented-out code findings →

Config drift 23 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

medium [AUC009] Sensitive function route lacks elevated authorization evidence: A rout… apps/dashboard/src/app/api/remote-development-env…:9
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… packages/shared/src/utils/html.tsx:56
low File has no detected symbols: hexclave.config.ts
low File has no detected symbols: apps/dashboard/tailwind.config.ts
low File has no detected symbols: apps/dashboard/postcss.config.js
low File has no detected symbols: apps/dashboard/vitest.config.ts
low Stray `console.log` in TS/JS — apps/dev-launchpad/scripts/write-env-config.js:11
low Stray `console.log` in TS/JS — apps/hosted-components/vite.config.ts:65
info TODO/FIXME marker in shipping code — apps/backend/src/lib/config.tsx:36
info TODO/FIXME marker in shipping code — packages/shared/src/config/schema.ts:1
low Stray `console.log` in TS/JS — packages/cli/src/commands/config-file.ts:252
low Stray `console.log` in TS/JS — examples/tanstack-start-demo/vite.config.ts:55

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/e6d37d74-7754-4561-8538-b052c5edecdf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e6d37d74-7754-4561-8538-b052c5edecdf/

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.