slither

Compile the project first with forge build, then run slither . from the project root. Slither reads Foundry's compilation artifacts and remappings.txt automatically; if detection fails, force it with --compile-force-framework foundry.

Filter dependency paths with --filter-paths "lib/|node_modules/", exclude noise detectors like naming-convention and solc-version, and use --triage-mode to interactively hide findings. Persist decisions in slither.db.json and settings in .slither.conf.json.

Slither is a static analyzer that scans code patterns in under a second with medium-high false positives. Mythril uses symbolic execution, Echidna uses fuzzing, and both find different bug classes more slowly. Use Slither on every commit and the others before audits.

Slither cannot resolve remapped imports when remappings.txt is missing or submodules are uninitialized. Run git submodule update --init --recursive, regenerate with forge remappings > remappings.txt, or set solc_remaps in .slither.conf.json.

Yes, subclass AbstractDetector with ARGUMENT, IMPACT, and WIKI attributes, implement _detect() using the compilation unit API, and run it via --plugin-detect or install it as a pip package with a slither_analyzer.plugin entry point.

Slither examines code structure without execution, so it cannot catch runtime logic errors, economic exploits, or oracle manipulation. Expect 30-60% false positives on real projects, and complement it with fuzzing, formal verification, and manual review.