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.

seeker71/Coherence-Network

https://github.com/seeker71/Coherence-Network · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

1014 raw signals (0 security + 1014 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 945 actionable findings from 1 signal source. 69 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 · 945 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 275 Medium 165 Low 184 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 945 Crowd 0 Layer: Software 12 Frontend 83 Network 5 Hardware 8 Security 282 Cicd 3 Quality 480 Api 72

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 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 10 places
low Near-duplicate function bodies in 6 places repo-level
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 7 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

medium Insecure pattern 'weak_hash' in docs/system_audit/model_executor_run_ledger/leg… docs/system_audit/model_executor_run_ledger/legac…:18
low Old/deprecated-named symbol `parseTypeScriptLegacy` in form/form-kernel-ts/seed…

View all legacy markers findings →

Commented-out code 273 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 (6 lines) in form/form-kernel-rust/test_serve.py:287
info Commented-code block (9 lines) in form/form-kernel-rust/router_header_passthrou…
info Commented-code block (7 lines) in form/form-kernel-rust/production_routes_harne…
info Commented-code block (5 lines) in form/form-kernel-rust/router_body_harness.py:…
info Commented-code block (6 lines) in form/form-kernel-rust/router_upstream_reuse_h…
info Commented-code block (20 lines) in form/form-kernel-ts/seedbank/python-adapter/…
info Commented-code block (7 lines) in form/form-kernel-ts/seedbank/python-adapter/e…
info Commented-code block (6 lines) in form/form-kernel-ts/seedbank/python-adapter/e…
info Commented-code block (9 lines) in form/form-kernel-ts/seedbank/python-adapter/e…
info Commented-code block (6 lines) in form/form-kernel-ts/seedbank/python-adapter/e…
info Commented-code block (6 lines) in form/form-kernel-ts/seedbank/python-adapter/e…
info Commented-code block (6 lines) in form/form-kernel-ts/seedbank/python-adapter/e…

View all commented-out code findings →

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

8 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (7 lines) in cli/lib/config.mjs:16
info Commented-code block (7 lines) in web/next.config.ts:49
medium `fetch()` without try/.catch or AbortSignal — web/app/diagnostics/config-editor…
info Commented-code block (6 lines) in web/lib/public-config.ts:54
info Commented-code block (5 lines) in web/lib/app-config.ts:11
high FastAPI PATCH `patch_config` without auth dependency — api/app/routers/meta.py:… api/app/routers/meta.py:196
high FastAPI PATCH `update_routing_config` without auth dependency — api/app/routers… api/app/routers/models.py:524

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/51db0f09-ad22-4d27-98be-e13e3506533e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/51db0f09-ad22-4d27-98be-e13e3506533e/

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.