AgentsMesh/AgentsMesh

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.

Scan timing: clone 8.25s · analysis 33.02s · 34.1 MB · GitHub API rate-limit (preflight)

https://github.com/AgentsMesh/AgentsMesh · scanned 2026-05-31 01:23 UTC (1 week, 6 days ago) · 10 languages

918 raw signals (230 security + 688 graph) 11/13 scanners ran 80th percentile · Go · huge (>500K LoC) System graph score 85 (higher by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 6 days ago · v2 · last Δ +2.3 (diff) · 479 actionable findings from 2 signal sources. 154 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 · 396 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	95.0	0.20	19.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	82.0	0.15	12.30
`code_quality`	80.0	0.10	8.00
Overall		1.00	88.3

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 30 Medium 42 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 396 Crowd 0 Layer: Quality 252 Security 38 Cicd 13 Software 56 Frontend 118 Network 1 Hardware 1

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.

Commented-out code 197 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 (9 lines) in packages/service-runtime/src/service-getters.…
info Commented-code block (7 lines) in packages/electron-adapter/src/auth.ts:126
info Commented-code block (6 lines) in packages/electron-adapter/src/provider.ts:93
info Commented-code block (7 lines) in packages/electron-adapter/src/state_adapters.…
info Commented-code block (5 lines) in packages/electron-adapter/src/channel_state.t…
info Commented-code block (8 lines) in packages/electron-adapter/src/repository.ts:4
info Commented-code block (5 lines) in packages/electron-adapter/src/agent.ts:5
info Commented-code block (5 lines) in packages/electron-adapter/src/env_bundle.ts:1
info Commented-code block (10 lines) in proto/gen/ts/ticket/v1/ticket_pb.ts:3
info Commented-code block (7 lines) in proto/gen/ts/env_bundle/v1/env_bundle_pb.ts:6
info Commented-code block (16 lines) in proto/gen/ts/notification/v1/notification_pb…
info Commented-code block (6 lines) in proto/gen/ts/channel_state/v1/channel_state_p…

View all commented-out code findings →

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

12 matching findings on this repo

low File has no detected symbols: clients/web-admin/vitest.config.ts
low File has no detected symbols: clients/web-admin/next.config.ts
low Stray `console.log` in TS/JS — clients/web/next.config.ts:117
info `truncate` class without `title=` for hover reveal — clients/web/src/components…
info `truncate` class without `title=` for hover reveal — clients/web/src/app/(dashb…
info Commented-code block (9 lines) in clients/web-admin/vitest.config.ts:10
info Commented-code block (8 lines) in clients/web-admin/next.config.ts:3
info Commented-code block (6 lines) in clients/desktop/electron.vite.config.ts:13
info Commented-code block (6 lines) in clients/desktop/src/main/server_config.ts:12
info Commented-code block (8 lines) in clients/web/vitest.config.ts:10
info Commented-code block (10 lines) in clients/web/next.config.ts:14
info Commented-code block (9 lines) in clients/web/e2e-playwright/tests/pod/acp-ui-c…

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/06c71da3-6aea-4bfe-bd59-59aeea878bff/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/06c71da3-6aea-4bfe-bd59-59aeea878bff/

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.