Cryptographically verifiable, distributed dependency reviews
reviewer: matthiasbeyer
$ cargo crev repo fetch url https://github.com/matthiasbeyer/crev-proofs
$ cargo crev id trust HT24oErbY-0x-yt9mGMZEk5S07lzpFQ4kayzEkVxJWU
repo: https://github.com/matthiasbeyer/crev-proofs
Please, use mobile in landscape.
I am one of the current maintainers of the crate and feel confident to say
that the crate is safe to use.
I am one of the current maintainers of the crate and feel confident to say
that the crate is safe to use.
I know that there's one line unsafe in this crate, which is necessary for
zero-copying reasons.
I am positive that the crate is completely safe to use and I know the author
personally.
Not much code and easy to understand. As of today, the crate has no CI in
place, which may concern some. But it seems to be rather feature-complete.
Am the current maintainer of the crate, no dramatic changes since 0.13.2.
I am the current maintainer of the project and am reasonably confident that
there are no major issues with the codebase besides the documented one in the
github issue tracker.
Pretty straight-forward code, looks good.
Very well documented and (doc-)tested.
Had a look, it is literally only a hand full of lines and there's nothing that
made me lift an eyebrow...
Crate is just a collection of constants with some conveniance functionality
added. Should be perfectly fine to use, although the crate seems to be no
longer maintained.
I am the author and am confident that this crate works as advertised.
Code is pretty easy to understand and seems reasonable. No unsafe found.
I am the author and maintainer of this crate.
I am the author and am confident that this crate works as advertised.
No major issues found.
I am the author and am confident that the crate works as advertised.
Was invovled in writing this crate, but am not the main author.
Was invovled in writing this crate, but am not the main author.
I have been involved in writing this crate (not primary author though).
Crate should be perfectly fine to use.
I am the co-author of this crate and am confident about it.
Minor changes to the windows parts (did not look too closely). Most prominent
change seems to be lazy_static to be relaced with once_cell.
Only one instance of unsafe code which seems ok to me (though I am not
experienced with unsafe code). Did not have a look at the cfg(windows) code
parts.
© bestia.dev 2023, MIT License, Version: 2023.608.1636
Open source repository for this web app: https://github.com/bestia-dev/cargo_crev_web/
Simple codebase, looks good. Did not look at the cfg(windows) code.