1.1.0 (current)
From google/supply-chain copy of chromium. By George Burgess IV.
This review is from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.1.0 (current)
From google/supply-chain copy of chromium. By George Burgess IV.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
Excellent soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-1
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use does-not-implement-crypto
,
which implies crypto-safe
, but does not require expert review in order to
audit for.
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of nb is 1.1.0.
1.0.0 (older version) Thoroughness: Medium Understanding: Medium
Approved without comment by robin-nitrokey on 2021-12-03
1.0.0 (older version) Thoroughness: High Understanding: Medium
Approved without comment by szszszsz on 2021-12-03
1.0.0 (older version) Thoroughness: High Understanding: Medium
by crjeder on 2021-08-02
Minimal and basic code. Maintained by the HAL team. Trustworthy.
1.0.0 (older version) Thoroughness: Low Understanding: Medium
by gitlab.com/chrysn on 2021-02-02
Changes since 0.1.2 were largely cosmetic.
0.1.3 (older version) Thoroughness: Medium Understanding: Medium
Approved without comment by robin-nitrokey on 2021-12-03
0.1.3 (older version) Thoroughness: High Understanding: Medium
Approved without comment by szszszsz on 2021-12-03
0.1.3 (older version) Thoroughness: Medium Understanding: Medium
by crjeder on 2021-08-04
Minimal crate with no depedenscies. Trustworty.
0.1.2 (older version) Thoroughness: Low Understanding: Medium
Approved without comment by gitlab.com/chrysn on 2020-01-20
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository with a git tag matching the version. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.
To review the actual code of the crate, it's best to use cargo crev open nb
. Alternatively, you can download the tarball of nb v1.1.0 or view the source online.
rg -i unsafe
resulted in zero hits for this package.