Community and governance

Only the latest release receives security updates. Report undisclosed vulnerabilities privately through GitHub private vulnerability reporting, if available, or contact the maintainer privately through GitHub. Do not open a public issue. Include the affected version, reproduction steps, expected and actual behavior, and relevant logs without sensitive information.

Open a focused branch, make and test your changes, then submit a pull request explaining the change, its purpose, and the checks performed. Bug reports should include the version, OS, architecture, reproduction steps, and expected and actual behavior. Keep CLI documentation and translations in sync; explain packaging impacts and validation when relevant.

Contributors are expected to keep project discussions and collaboration respectful and constructive.

Use Rust, Cargo, Git, and system curl. The Rust dependency is thiserror 2. Unix tests also use Git to verify patch application. Run the relevant checks below before submitting code. Documentation and translation contributions are welcome; GNU gettext tools are needed to refresh po/patchsplit.pot with scripts/update-pot.sh.

cargo build --release --locked
cargo fmt --check
cargo check --locked
cargo test --locked
cargo clippy --locked --all-targets --all-features -- -D warnings