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.

wing1008/codesynapt

https://github.com/wing1008/codesynapt · scanned 2026-06-16 00:58 UTC (2 months, 1 week ago)

133 raw signals (0 security + 133 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 24 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 127 Crowd 0 Layer: Software 1 Frontend 8 Security 15 Cicd 5 Quality 91 Api 7

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 6 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.

6 matching findings on this repo

low Old/deprecated-named symbol `auditLegacy` in electron/main.cjs:217
low Old/deprecated-named symbol `getLegacy` in electron/preload.cjs:199
low Old/deprecated-named symbol `auditLegacy` in tests/accuracy-edges.test.js:4
low Old/deprecated-named symbol `vN_old` in packages/core/legacy.js:33
info Commented-code block (5 lines) in packages/core/legacy.js:9
low Old/deprecated-named symbol `openLegacy` in public/app.js:5448

View all legacy markers findings →

Commented-out code 65 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 (16 lines) in server.js:59
info Commented-code block (6 lines) in electron/plugin-loader.cjs:4
info Commented-code block (6 lines) in electron/main.cjs:4
info Commented-code block (7 lines) in electron/preload.cjs:6
info Commented-code block (6 lines) in tests/coverage-langs.test.js:13
info Commented-code block (5 lines) in tests/cli-symbol.test.js:11
info Commented-code block (6 lines) in tests/accuracy-edges.test.js:91
info Commented-code block (6 lines) in tests/viewer-client.test.js:1
info Commented-code block (5 lines) in tests/lang-completeness/js.test.js:4
info Commented-code block (5 lines) in tests/lang-completeness/go.test.js:4
info Commented-code block (6 lines) in tests/lang-completeness/flow-honest.test.js:6
info Commented-code block (8 lines) in tests/lang-completeness/cjs-require-callers.t…

View all commented-out code 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/7350c8da-560d-42b2-9e06-2e1bfce600b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7350c8da-560d-42b2-9e06-2e1bfce600b1/

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.