0.5.0 (current)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
0.5.0 (current)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
0.5.0 — diff review from 0.4.1 only (current)
From bytecodealliance/wasmtime. By Alex Crichton.
0.5.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.5.0 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (experimental). Changelog:
The current version of heck is 0.5.0.
0.4.1 — diff review from 0.4.0 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.4.1 (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
Grepped for -i cipher
, -i crypto
, 'fs'``,
'net', `'unsafe'
and there were no hits.
heck
(version 0.3.3
) has been added to Chromium in
https://source.chromium.org/chromium/chromium/src/+/28841c33c77833cc30b286f9ae24c97e7a8f4057
0.4.1 — diff review from 0.4.0 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
0.4.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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.
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
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
May have been packaged automatically without a review
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of heck is 0.5.0.
0.4.0 (older version) Thoroughness: High Understanding: High
by LovecraftianHorror on 2022-11-23
Simple, clean implementation, well documented, and a concise set of tests. Can't really ask for much more.
0.3.1 (older version) Thoroughness: Medium Understanding: High
Approved without comment by kpcyrd on 2019-08-30
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. 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 heck
. Alternatively, you can download the tarball of heck v0.5.0 or view the source online.
Minor changes for a
no_std
upgrade but otherwise everything looks as expected.