Slither Detector Result Explainer

WHAT IT DOES

Slither Detector Result Explainer takes the JSON output from a Slither static analysis run and transforms each detector finding into a structured, human-readable explanation. It parses the Slither results, extracts detector names, severity levels, descriptions, and source locations, then enriches each finding with a curated knowledge base of explanations. For each detector, the tool provides: the vulnerability name, a plain-English description, a detailed explanation of why the pattern is dangerous, a list of potential impacts, and a concrete suggestion for remediation. The output is organized by severity (Critical → High → Medium → Low → Info) with a summary bar showing the count of findings at each level. This turns raw Slither output — which can be cryptic and technical — into actionable security guidance that developers can immediately understand and apply.

HOW TO USE

Run Slither on your contract using the command: slither . --json or slither MyContract.sol --json. Copy the entire JSON output and paste it into the text area on this page. Optionally, enter the contract address for context (the tool does not verify the address, but you can use it for your own reference). Click "Explain findings" to parse and enrich the results. The tool displays each finding as a card showing the detector name, severity badge, affected source location, a description pulled from Slither, a detailed explanation from the knowledge base, the potential security impacts, and a remediation suggestion. Use this to quickly triage audit results, prioritize fixes, or understand what Slither is telling you before diving into the source code.

THE REAL MECHANISM — why this beats reading raw Slither output

Raw Slither JSON contains detector names like "reentrancy-eth", "unchecked-lowlevel", or "tx-origin" with terse descriptions and bytecode references. This tool maps each detector name to a curated explanation entry that includes a human-readable title, a multi-sentence explanation of the vulnerability, a list of concrete impacts, and a remediation suggestion. The mapping covers the most common Slither detectors: reentrancy (ETH and non-ETH), unchecked low-level calls, tx.origin usage, block.timestamp manipulation, assembly usage, selfdestruct, divide-before-multiply precision loss, missing events, and arbitrary ETH sends. The parser handles multiple Slither output formats, including the standard --json format (with results.detectors), flattened detector arrays, and the raw list format. It also extracts source location information from each detector's elements array, showing you exactly which contract and line number is affected. The output is then sorted by severity, with Critical and High findings presented first, so you can focus on the most dangerous issues immediately. A summary bar at the top gives you an at-a-glance view of the risk profile of your contract.

WHAT IT CANNOT SEE

- Cannot verify if the Slither results you paste are from the same contract version as the deployed bytecode on-chain — you must ensure the JSON matches the contract you are reviewing.

- Cannot detect issues that Slither itself does not detect — this tool only explains what Slither found; it cannot add new detections or run the analysis for you.

- Cannot provide context about false positives without manual review — Slither sometimes flags safe patterns; the tool cannot determine if a finding is a real vulnerability or a false positive.

- Cannot explain findings that require knowledge of the specific contract's business logic — some vulnerabilities depend on how the contract is used in practice, which the tool cannot know.

- Cannot determine if a finding is actually exploitable in the current chain state without runtime analysis or a full manual audit.

- Cannot supplement missing Slither detections — if Slither missed a vulnerability, the tool will not catch it either.

- Cannot run Slither itself — you must run Slither locally and paste the output.

- Cannot decode results from other static analysis tools (e.g., Mythril, Oyente, Securify) — only Slither JSON format is supported.

PLEASE NOTE

This tool works with Slither output from Solidity contracts on any EVM-compatible chain. It does not run analysis; it only explains existing Slither results. The tool is read-only — it never sends transactions. No data is stored remotely; all processing happens in your browser. The explanations are heuristic and may not cover every Slither detector — if a detector is missing from the knowledge base, the tool falls back to a generic explanation. Always use this tool as a starting point, not a substitute for professional security review, manual code inspection, or formal verification. For the most up-to-date Slither detectors, consult the official Slither documentation alongside this tool.