building-secure-contracts VS slither

I appreciate how organized the Consensys guide is laid out. It's pretty easy to read. Trail of Bits has a similar guide that is a little more in-the-weeds technically. It also covers, what we think is, essential background about certain automated analysis techniques like static analysis and how fuzzers work. Check it out!

https://secure-contracts.com/

We highly recommend using at least one of them if professional contract security review is not possible. A more comprehensive look into secure development practices can be found here.

If you need more reading about building secure smart contracts and auditing workflows, see here: https://github.com/crytic/building-secure-contracts

Yes exactly! However, >99% of the time this wouldn't happen unintentionally, and typically static analysis frameworks will detect function clashing like slither: https://github.com/crytic/slither.

I don't know these tools but took a look at the slither-analyze deps, and see that solc-select is not a hard dependency, but part of the extra dep group called dev. So with a normal pipx install slither-analyze, solc-select is probably absent from the relevant venv.

Congrats, you just wasted money for an audit you could have done for free with https://github.com/crytic/slither.

Vulnerability Infrastructure: Slither

What are the differences of your solution to `slither documentation`?