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, exclude noise detectors like naming-convention and solc-version, and use --exclude-informational and --exclude-optimization. Persist decisions with --triage-mode, which saves hide/show choices to slither.db.json.

Slither is a fast static analyzer that finds known code patterns in under a second but has a medium-high false positive rate. Mythril uses symbolic execution, and Echidna is a fuzzer for invariant testing; the recommended workflow layers Slither first, then fuzzing or formal verification.

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

Yes, subclass AbstractDetector, define ARGUMENT, IMPACT, CONFIDENCE, and WIKI fields, and implement _detect() using the Slither Python API. Run it with --detect your-detector-id --plugin-detect path/to/file.py or package it with a slither_analyzer.plugin entry point.

Slither examines code structure without executing it, so it cannot catch runtime logic errors, economic exploits, or oracle manipulation. Expect a 30-60% false positive rate, and complement it with fuzzing, formal verification, and manual review.