crytic / crytic/slither-action
[Bug-Candidate]: Foundry project with node module dependencies can not be analyzed in github action.
- Dominant language
- Shell
- Stars
- 142
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the issue:
I am running slither check in my github ci workflow, but can't pass due to some issues.
The main problem is that my foundry project is using node module dependencies, not gitsubmodules.
And seems like slither is not able to build or use build-info in out directory.
### Code example to reproduce the issue:
https://github.com/Lay3rLabs/poa-middleware/blob/feat/ci-workflow/.github/workflows/slither.yml
https://github.com/Lay3rLabs/poa-middleware/actions/runs/17726391325/job/50367849144?pr=10
### Version:
0.11.3
### Relevant log output:
```shell
https://github.com/Lay3rLabs/poa-middleware/actions/runs/17726391325/job/50367849144?pr=10
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/slither.yml and the linked GitHub Actions run, using the reported version 0.11.3 as the baseline. Reproduce the failure with a Foundry project that uses node module dependencies rather than git submodules; done means the workflow can analyze the project successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100