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.

bklassen3434/agent-mesh

https://github.com/bklassen3434/agent-mesh · scanned 2026-06-17 01:40 UTC (1 month, 1 week ago)

60 raw signals (0 security + 60 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -9.6 (diff) · 45 actionable findings from 1 signal source. 15 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 6 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places
View all duplicates & near-duplicates findings →
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 `test_default_env_wins_over_legacy` in tests/test_l…
View all legacy markers findings →
Commented-out code 9 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/`.
9 matching findings on this repo
  • info Commented-code block (8 lines) in packages/mesh-llm/src/mesh_llm/prompts.py:707
  • info Commented-code block (5 lines) in packages/mesh-agents/src/mesh_agents/connecto…
  • info Commented-code block (5 lines) in packages/mesh-db/src/mesh_db/episodic.py:121
  • info Commented-code block (6 lines) in packages/mesh-db/src/mesh_db/search.py:57
  • info Commented-code block (5 lines) in packages/mesh-db/src/mesh_db/beliefs.py:14
  • info Commented-code block (6 lines) in packages/mesh-models/src/mesh_models/claim.py…
  • info Commented-code block (6 lines) in packages/mesh-models/src/mesh_models/connecto…
  • info Commented-code block (5 lines) in apps/pipeline/src/mesh_pipeline/belief_consol…
  • info Commented-code block (5 lines) in apps/pipeline/src/mesh_pipeline/coordinator.p…
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/bb6bedc4-5b30-4570-920c-808ad3554894/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bb6bedc4-5b30-4570-920c-808ad3554894/

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.