-
Notifications
You must be signed in to change notification settings - Fork 24
Add cargo-audit security scan to CI #97
Copy link
Copy link
Open
Labels
Stellar WaveDrips Wave program issueDrips Wave program issuearea:ciCI/CD and toolingCI/CD and toolingarea:contractsSoroban contractsSoroban contractsdifficulty:easy~1-3 hours~1-3 hoursgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Metadata
Metadata
Assignees
Labels
Stellar WaveDrips Wave program issueDrips Wave program issuearea:ciCI/CD and toolingCI/CD and toolingarea:contractsSoroban contractsSoroban contractsdifficulty:easy~1-3 hours~1-3 hoursgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Background
The Soroban smart contracts have Cargo dependencies that could contain known CVEs. Adding
cargo auditto CI automatically fails the build if a vulnerability is detected in any transitive dependency, keeping the contracts secure without manual tracking.What to build
Add a CI job that runs
cargo auditagainst the contracts workspace on every PR targetingmain.Key files
.github/workflows/ci.yml— add a new job herecontracts/Cargo.lock— must be committed forcargo auditto workSuggested execution
security-auditjob to.github/workflows/ci.ymlthat installscargo-auditand runs it fromcontracts/contracts/Cargo.lockis committed (check.gitignore)audit.tomlwith a justification commentExample commit message:
ci: add cargo-audit security scan for Soroban contract dependenciesAcceptance criteria
audit.toml