Argyle-Software / Argyle-Software/sphincsplus
Cleanup function visibilty
Open
good first issue
- Dominant language
- Rust
- Stars
- 24
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Many functions are marked public when they don't need to be, this is an easy cleanup job for anyone interested.
Contributor guide
Research direction
Start by surveying the Rust codebase for functions marked public and determine which visibility changes are safe for the implementation. The issue does not name files, tests, or entry points, so first identify the affected functions and any public API expectations. Done means unnecessary public visibility is removed without breaking the Sphincs+ implementation or its tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100