PLSysSec / PLSysSec/cargo-scan
Sanity check: check that call graph is complete
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Check that for each node in the call graph, we also have scanned its definition (or can find it in a dependency, or it's an FFI call)
This is a good sanity check to make sure we're not silently missing large sections of the call graph or mapping function calls to an identifier we don't recognize.
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 call-graph construction and node-resolution logic in the Rust tool, then trace how definitions, dependency functions, and FFI calls are represented. Add a sanity check that every call-graph node is accounted for by one of those cases, and cover missing or unrecognized identifiers with tests. Done means the scan reports incomplete graph coverage instead of silently accepting unresolved nodes.
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
- Mostly clear
- Newbie friendliness
- 35/100