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.

seanssoh/agent-bridge-public

https://github.com/seanssoh/agent-bridge-public · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

363 raw signals (0 security + 363 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 338 actionable findings from 1 signal source. 25 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 338 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 6 Medium 61 Low 127 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 338 Crowd 0 Layer: Software 32 Network 14 Frontend 1 Security 12 Cicd 2 Quality 277

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

2 matching findings on this repo

low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

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

10 matching findings on this repo

low File has no detected symbols: scripts/smoke/1108-helpers/assert-legacy-watchdog…
low File has no detected symbols: lib/upgrade-helpers/auth-legacy-claude-config-env…
low Very large file: scripts/python-helpers/migrate-legacy-install-helper.py (1547 …
low Old/deprecated-named symbol `_probe_legacy` in bridge-memory.py:2789
low Old/deprecated-named symbol `abs_legacy` in bridge-runtime-inventory.py:483
low Old/deprecated-named symbol `agent_root_v2` in scripts/python-helpers/migrate-l…
info Commented-code block (7 lines) in scripts/python-helpers/migrate-legacy-install…
medium Network/subprocess call without timeout or try/except — scripts/python-helpers/…
info Commented-code block (13 lines) in scripts/python-helpers/prune-legacy-teams-mc…
low Old/deprecated-named symbol `exc_legacy` in scripts/smoke/usage-probe-edge-clas…

View all legacy markers findings →

Commented-out code 139 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 bridge_orphan_classifier.py:64
info Commented-code block (8 lines) in bridge-queue.py:21
info Commented-code block (8 lines) in bridge-orphan-gc.py:161
info Commented-code block (11 lines) in bridge-cron.py:37
info Commented-code block (5 lines) in bridge-dev-plugin-cache.py:74
info Commented-code block (6 lines) in bridge-auth.py:37
info Commented-code block (6 lines) in bridge_rooms_common.py:81
info Commented-code block (7 lines) in bridge-status.py:21
info Commented-code block (5 lines) in bridge_a2a_common.py:44
info Commented-code block (5 lines) in bridge-wave.py:235
info Commented-code block (6 lines) in bridge-doctor.py:59
info Commented-code block (5 lines) in bridge-relay-cleanup.py:402

View all commented-out code findings →

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

6 matching findings on this repo

low File has no detected symbols: lib/upgrade-helpers/auth-legacy-claude-config-env…
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in bridge-config.py:83
info Commented-code block (5 lines) in scripts/python-helpers/seed-operator-plugin-c…
info Commented-code block (5 lines) in scripts/python-helpers/seed-claude-first-run-…
info Commented-code block (6 lines) in lib/system_config_paths.py:33

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/ebf13555-b50b-4b93-a762-848f312c99d5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ebf13555-b50b-4b93-a762-848f312c99d5/

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.