crytic / crytic/echidna-action
Option to only have echidna installed via action
- Dominant language
- Shell
- Stars
- 61
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to have the ability to only install echidna to then be able to use/call it via other scripts, the same that [foundry-toolchain](https://github.com/foundry-rs/foundry-toolchain) allows it. In my case I'm trying to run a python script that executes a bunch of tests/challenges sequentially using echidna and foundry and measure performance (test outcomes, execution time & perhaps more later).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the action's workflow and entry-point configuration to see how Echidna is currently installed. Compare its inputs and behavior with foundry-toolchain, then verify that a workflow can install Echidna without running it and that a later Python or shell step can invoke it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python, shell
- Domain
- ci-cd, cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100