Emilio López

Looking at the Hardhat issue tracker, this might be related: https://github.com/NomicFoundation/hardhat/issues/3877

Hi! This is a known foundry bug, being tracked upstream here https://github.com/foundry-rs/foundry/issues/7014 slither / crytic-compile query `foundry config --json` to learn information such as the the EVM version, but foundry...

as a workaround, you can add a `- run: rm foundry.toml` step on your workflow before invoking the action; this will cause foundry to not be detected and therefore installation...

hey @thedavidmeister! The Slither action runs inside a container so any existing foundry installations on the github runner are unfortunately inaccesible. If you'd like to use a foundry installation on...

hey @PaulRBerg, the Slither action just runs `forge install` there to install any possible dependencies your project may have. https://github.com/crytic/slither-action/blob/main/entrypoint.sh#L233-L234 I can reproduce the same error locally on a clone...

This is possibly related to https://github.com/NomicFoundation/hardhat/issues/3877 -- see also https://github.com/crytic/slither-action/issues/56 As a workaround, downgrading Node can resolve the failures.

Hi @duckki, that error message seems to be unrelated. The repo you linked has a custom `out` folder name, which crytic-compile cannot autodetect yet: https://github.com/code-423n4/2023-01-ondo/blob/main/foundry.toml#L4 You can either remove that...

I'll close this issue now but feel free to open a new one if you are still having issues.

@dependabot rebase

I am using the WebIDE for the time being, very handy tool to learn 👍 I guess a mechanism to promote integer types to longer ones would be the better...