PLSysSec / PLSysSec/cargo-scan
Build-time effects
Open
Nobody has claimed this yet.
roadmap-v0
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
run on build.rs scripts and macro invocations and produce reasonable output
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
Start by locating the code that scans Rust crates and determine how build.rs scripts and macro invocations are currently handled. Exercise both cases with representative crates, then verify that the tool completes and produces reasonable output for each.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100