0.1.5 (current)
From mozilla/supply-chain copy of mozilla/glean. Audited without comment by Jan-Erik Rediger.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
0.1.5 (current)
From mozilla/supply-chain copy of mozilla/glean. Audited without comment by Jan-Erik Rediger.
0.1.5 (current)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
The current version of unicode-linebreak is 0.1.5.
0.1.4 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.1.4 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
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…
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.
May have been packaged automatically without a review
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of unicode-linebreak is 0.1.5.
0.1.1 (older version) Thoroughness: High Understanding: High
by mgeisler on 2021-05-07
Nice crate which uses a build script to auto-generate the character
tables at compile time. Has one instance of unsafe
where a u8
is
cast to an enum. The enum is marked as repr(u8)
to make this safe.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open unicode-linebreak
. Alternatively, you can download the tarball of unicode-linebreak v0.1.5 or view the source online.
Grepped for
-i cipher
,-i crypto
,'fs'``,
'net', `'unsafe'
and there were no hits.Version
0.1.2
of this crate has been added to Chromium in https://source.chromium.org/chromium/chromium/src/+/591a0f30c5eac93b6a3d981c2714ffa4db28dbcb The CL description contains a link to a Google-internal document with audit details.