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.

welshDog/HyperCode-V2.4

https://github.com/welshDog/HyperCode-V2.4 · scanned 2026-06-16 00:57 UTC (2 months, 1 week ago)

588 raw signals (0 security + 588 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 371 actionable findings from 1 signal source. 217 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 · 371 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 122 Medium 96 Low 127 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 371 Crowd 0 Layer: Software 26 Frontend 26 Network 4 Hardware 28 Security 119 Cicd 5 Quality 86 Api 77

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 11 places
low Near-duplicate function bodies in 8 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 7 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.

7 matching findings on this repo

low Stray `console.log` in TS/JS — archive/legacy/agents-dashboard-legacy/component…
medium Insecure pattern 'direct_innerhtml_assignment' in archive/legacy/agents-dashboa… archive/legacy/agents-dashboard-legacy/index.html:299
medium Insecure pattern 'direct_innerhtml_assignment' in archive/legacy/agents-dashboa… archive/legacy/agents-dashboard-legacy/components…:86
low Old/deprecated-named symbol `unstable_legacy` in reports/e2e-html/trace/assets/…
high FastAPI POST `reset_circuit_breaker` without auth dependency — archive/legacy/n… archive/legacy/new-fix-0.1/FIX_2_healer_main_impr…:349
high FastAPI POST `trigger_heal` without auth dependency — archive/legacy/new-fix-0.… archive/legacy/new-fix-0.1/FIX_2_healer_main_impr…:357
high Dangling fetch: POST http://localhost:8080/approvals/respond (archive/legacy/ag…

View all legacy markers findings →

Commented-out code 17 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 tests/test_swarm_load.py:2
info Commented-code block (5 lines) in tests/functional/test_coder_capabilities.py:6
info Commented-code block (15 lines) in verification/test_coder_agent_protocol.py:55
info Commented-code block (6 lines) in agents/dashboard/__tests__/Clock.test.tsx:31
info Commented-code block (6 lines) in agents/dashboard/components/panels/AgentDetai…
info Commented-code block (7 lines) in agents/dashboard/hooks/useAgentStatus.ts:1
info Commented-code block (6 lines) in agents/crew-orchestrator/tests/test_orchestra…
info Commented-code block (8 lines) in agents/broski-bot/tests/test_enterprise.py:143
info Commented-code block (6 lines) in agents/broski-bot/alembic/env.py:95
info Commented-code block (8 lines) in agents/broski-bot/src/services/quest.py:113
info Commented-code block (5 lines) in agents/broski-bot/src/cogs/quest_system.py:105
info Commented-code block (8 lines) in hyperstudio-platform/api-main.py:525

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/skills/hypercode-mcp-gate… .claude/skills/hypercode-mcp-gateway/SKILL.md:53
high Agent instruction/config may expose a secret: .claude/skills/hypercode-hyperfoc… .claude/skills/hypercode-hyperfocus-builder/SKILL…:225
high Agent instruction/config may expose a secret: .claude/skills/hypercode-supabase… .claude/skills/hypercode-supabase/SKILL.md:38
high Agent instruction/config may expose a secret: .claude/skills/technical-skills-a… .claude/skills/technical-skills-audit/security-gu…:37

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/9a9895ab-0fb4-4600-8c1a-10d7c7977f54/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9a9895ab-0fb4-4600-8c1a-10d7c7977f54/

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.