PLSysSec / PLSysSec/cargo-scan
Dependency fencing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
another idea to support: fencing dependencies -- crate U is restricted and can only be used by certain trusted dependencies X, Y, Z
in the workspace Cargo.toml, say "this dep can only be used by crate X, Y, Z"
(you can do this as a postprocessing step. maybe we should just make cargo fence for this down the road)
e.g.:
we're pulling in yubikey which pulls in pcsc-sys; this is only for thing son the cli side but we have a workspace where our server-side stuff lives too (but should never ever use this)
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 implementation file or test is named. Start by examining how cargo-scan processes workspace Cargo.toml dependencies and investigate whether a postprocessing step or cargo fence is the intended direction. Done would mean defining and enforcing that restricted dependencies such as pcsc-sys are usable only by the permitted crates.
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