Get help and give feedback
Choose the place that matches what you want to say. Public channels let others find the answer later; use email only for matters that should stay private.
| What you want to say | Where |
|---|---|
| A question about, or objection to, someone else's Report | The Report's Comments. See Discuss a report |
| Something you learned while verifying your own crate | A Finding on your Report. See Add findings |
A problem with the proofs.rs website or cargo proofs | Bug report on GitHub |
| A feature request or general feedback | Feedback on GitHub |
| A verification tool or tool version to support | Tool or version request on GitHub |
| A question about using proofs.rs or verification tools | Zulip |
| A security vulnerability in the service | Email contact@proofs.rs. Do not open a public issue |
| Account deletion, privacy, content, or licensing concerns | Email contact@proofs.rs |
Before you write
- About a Report: comment on the Report itself, not on GitHub or Zulip. The author is notified by email if they have notifications enabled, and later readers can see the question and its answer.
- About the service: include the page URL or the
cargo proofscommand, the CLI version (cargo proofs --version), and what you expected to happen. - By email: never send passwords or access tokens.
Found a bug in a crate while reading someone else's Report? Findings can be added only by the Report's author. Comment on the Report to tell the author, report it to the crate's own issue tracker, or verify the crate yourself and publish a Report with the Finding.
The proofs.rs source code, issue tracker, and development discussions are public on GitHub.