cargo-crev
cargo-crev copied to clipboard
A cryptographically verifiable code review system for the cargo (Rust) package manager.
We could `cargo-expand` for allowing reviewing the crate code conveniently without having to `cd` to a given directory. We should probably expand `build.rs` and any other file like this too.
I tried setting up `cargo crev` as a reviewer, using 0.21.3 installed from `cargo install`, on Arch Linux. I was unable to `cargo crev publish`. To reproduce this issue, I...
I am unable to use `crev fetch` with `git@` (ssh) URLs. ```bash > RUST_BACKTRACE=1 cargo crev fetch url [email protected]:dpc/crev-proofs.git Fetching [email protected]:dpc/crev-proofs.git... Error: authentication required but no callback set; class=Ssh (23)...
Hi! I am exploring `cargo-crev` for code review at my workplace. The reviews we would produce would be geared for our own use case and as such we would like...
Currently `crev verify` uses empty `TrustSet` when own id is not configured, but a completely empty set is not reporting anything. That makes a poor first impression. Some trusted reviews...
Things like editing files used to be in `crev-lib`, but then "library sould not be doing IO" so they were moved to `cargo-crev`, but then ... it's worthwhile to have...
https://github.com/daynin/fundoc
Consider a crate with versions 1.0 and 1.0.1, and two reviews by trusted reviewers, one reviewing 1.0 at a medium thoroughness and undestanding, and delta review 1.0 to 1.0.1at a...
Doing the initial review is only half the battle, keeping crates reviewed when new updates come out would be nice! My current workflow is to: * Review crate * Go...