korotovsky/slack-mcp-server

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.

https://github.com/korotovsky/slack-mcp-server · scanned 2026-05-14 22:54 UTC (3 weeks ago) · 10 languages

38 findings (17 legacy + 21 scanner) 62nd percentile · Go · small (2-20K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks ago · v1 · 14 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	90.6	0.25	22.65
`testing_score`	80.0	0.20	16.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	75.0	0.15	11.25
`code_quality`	62.2	0.10	6.22
Overall		1.00	80.1

Calibrated penalty buckets (security_score): agent: 2.2 Â· docker: 7.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 9 Medium 2 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 14 9-layer 0 Crowd 0 Layer: Cicd 7 Quality 7

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.

Fragile runtime 7 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

7 matching findings on this repo

medium Agent control bridge may listen on a network interface without visible auth docker-compose.toolkit.yml:8
medium Agent control bridge may listen on a network interface without visible auth docker-compose.dev.yml:7
medium Duplicated implementation block across source files pkg/provider/edge/userlist.go:26
medium Duplicated implementation block across source files pkg/provider/edge/fasttime/fasttime_x64.go:1
medium Duplicated implementation block across source files pkg/provider/edge/dms.go:41
low [ERR003] Ignored Error (Go): Ignoring error return values. pkg/handler/conversations.go:2289
low Generated build artifact directory is present at repository root build:1

View all fragile runtime 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/0d5abec3-be66-4d8f-bd41-1c17d218e26f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0d5abec3-be66-4d8f-bd41-1c17d218e26f/

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.