Emilio López

It looks like you don't have write permissions on the folder you ran the tool from: > PermissionError: [Errno 13] Permission denied: 'crytic-export' Make sure you can write there, or...

Hi, thanks for the report! Do you have an example repository you can share to make the structure more clear? Note that if you have a complex or unsupported build...

Hi! `--ignore-compile` only makes it not run the build command (i.e. the extra commands that slither says it's running at the beginning when you run it without `--ignore-compile`, e.g. `forge...

@ChiHaoLu hi, thanks for the report! could this be a change or regression in Foundry? can you check which `forge --version` you have working locally and failing on your workflow?

So far we suspect this might be caused by https://github.com/foundry-rs/foundry/issues/7878 If you have the option, installing an older Foundry release seems to work around the problem: `foundryup -v nightly-f625d0fa7c51e65b4bf1e8f7931cd1c6e2e285e9` Unfortunately...

The foundry issue has been resolved upstream and the latest nightly build includes the fix, can you retest your workflows and let us know if this is now working?

I think sorting them numerically is nicer than purely alphabetical sort, ~~but I'd be cautions on switching the order from newer -> older to older -> newer -- I think...

Merged the dev branch, resolved some conflicts, and extracted the sorting logic into its own function. If tests pass I think this would be good to go 👍 thanks for...

Hi! yes, this is a known issue; unfortunately Foundry applies these rules on the full absolute paths instead of on the relative paths to the project repository only. They seem...

@stong PR #606 should hopefully address this