PLSysSec / PLSysSec/cargo-scan
Update audits on diff
Open
Nobody has claimed this yet.
roadmap-v1
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Note to look at later once initial experiments and audits are complete:
we want a semantically meaningful diff calculator that uses static analysis, in tandem with the existing audit, to determine which parts of the code need to be looked at again.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing audit and the initial experiments, then determine the scope of a semantically meaningful diff calculator using static analysis alongside the audit. Done means identifying which parts of changed code need to be audited again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100