Rust

Events

This material is being used during the events organized in the Code-Mavens Meetup group.

Pick a Rust-based project you use.
Pick a Rust crate that your code directly depends on. They are listed in the Cargo.toml file.
Pick a Rust crate that your code indirectly depends on. They are listed in the Cargo.lock file.
Search on GitHub: A semi-popular, recently updated Rust project stars:100..1000 pushed:>2025-10-01 language:Rust
A recently updated crate or a crate in a category you are interested in. See Crates.io.
Pick a popular project and work on stale PRs. That is PRs where there is already good work, but the original author (of the PR) has vanished.
Use the Rust Digger once it is running again.

Link to VCS: Find the listing of the crate on Crates.io and check if it links to its VCS. If not, try to find the repository and send a PR to include the link. If you cannot find the repo then you cannot contribute to the project. You might want to send a message to the author expressing interest in contributing and asking if there is a public repository.
Testing:
- Run the tests of the crate locally or better yet in a Docker container. Report if there is any test failures or if there are difficulties in running the tests.
- Generate test coverage report using tarpaulin.
- Find holes in the test coverage, write tests to check parts of the code that were not tested yet.
CI
- If there are tests, check if there is a CI?
- Setting up CI: GitHub Actions or GitLab pipelines.
Dependencies
- Add dependabot for GitHub Actions and for the dependencies.
Code formatting
- Using cargo fmt --check check if the code is well formatted. If not open an issue suggestion to do it.
Linting
- Use cargo clippy to run the linter. Configure Clippy.
Fuzz testing
- test-fuzz
- fuzzing
Mutation testing with cargo-mutants
- See article on Mutation testing librsvg
Code complexity analyzis
- complexity
Refactoring
Code reading