Emilio López
Emilio López
friendly ping @nmote 😄 I would love to see this fixed in Semgrep
Hi! Do you see any errors when you run `crytic-compile .` on your project?
As @0xalpharush mentioned, you can run Slither (or crytic-compile if you don't care about the analysis) directly on the etherscan copy of the contracts as well: ``` crytic-compile 0x51bdbfcd7656e2c25ad1bc8037f70572b7142ecc --etherscan-apikey...
Hi! Can you post the complete Slither output? I don't think we have anything in particular that detects multiple SPDX licenses; what you're seeing might be an error/warning from solc...
If it's a solc error you need to solve it in the solidity code. Slither requires code that can be compiled successfully.
Hi, thanks for the report! can you provide a sample contract/project that triggers this issue? The full error trace and message you get on the console would be useful as...
Hi again! Your slither config file is invalid, the "solc" option only takes a string (a path to a solc binary). You probably want something more like the following instead:...
Hi, thanks for the report! Can you confirm what happens if you run the following? ``` slither . --compile-force-framework hardhat ```
Does `crytic-compile .` print any different error?
I had a look locally, the paths generated on the Hardhat artifacts seem to be a bit odd, in particular the ones for forge-std/console.sol. You can work around the issue...