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.

Dicklesworthstone/mcp_agent_mail_rust

https://github.com/Dicklesworthstone/mcp_agent_mail_rust · scanned 2026-06-17 01:28 UTC (1 month, 2 weeks ago)

232 raw signals (0 security + 232 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.8 (diff) · 185 actionable findings from 1 signal source. 47 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 · 185 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 11 High 2 Medium 24 Low 148 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 185 Crowd 0 Layer: Frontend 2 Network 14 Hardware 1 Security 15 Cicd 3 Quality 150

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

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

low Very large file: crates/mcp-agent-mail-core/src/legacy.rs (2466 lines)
low Very large file: crates/mcp-agent-mail-cli/src/legacy.rs (2857 lines)

View all legacy markers findings →

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

3 matching findings on this repo

low Very large file: crates/mcp-agent-mail-core/src/config.rs (5619 lines)
low Very large file: crates/mcp-agent-mail-core/src/mcp_config.rs (2214 lines)
medium Runtime service client appears to use placeholder configuration

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/446640bc-eacc-443a-b418-e43082be3c89/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/446640bc-eacc-443a-b418-e43082be3c89/

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.