0.11.1 (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.11.1 — diff review from 0.11.0 only (current)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
0.11.1 — diff review from 0.10.0 only (current)
From mozilla/supply-chain copy of hg. Audited without comment by bendk.
0.11.1 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
The current version of strsim is 0.11.1.
0.11.0 (older version)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
No unsafe
0.11.0 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.10.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
0.10.0 (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
Reviewed in https://crrev.com/c/5171063
Previously reviewed during security review and the audit is grandparented in.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- does-not-implement-crypto (implies crypto-safe)
-
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.
- crypto-safe
Implied by other criteria
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 impliescrypto-safe, but does not require expert review in order to audit for.- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- ub-risk-0 (implies ub-risk-1)
-
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
- ub-risk-1 (implies ub-risk-2)
Implied by other criteria
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
- ub-risk-2 (implies ub-risk-3)
Implied by other criteria
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
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
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
- ub-risk-4
Implied by other criteria
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
- unknown
-
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 strsim is 0.11.1.
0.10.0 (older version) Thoroughness: High Understanding: High
Approved without comment by johnlepikhin on 2022-11-04
0.9.3 (older version) Thoroughness: None Understanding: Medium
by leo60228 on 2021-09-28
changes seem clear
0.8.0 (older version) Thoroughness: Medium Understanding: Medium
by gitlab.com/phgsng on 2019-09-23
No build.rs. No use of unsafe code or calls into C libraries. String accesses using bounds checked APIs. No IO.
0.7.0 (older version) Thoroughness: Low Understanding: Medium
by Alxandr on 2019-07-13
I don't claim to understand all the algorithms, but it seems to do what it claims, and has a bunch of tests to showcase it.
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 strsim. Alternatively, you can download the tarball of strsim v0.11.1 or view the source online.
Only in debcargo (unstable). Changelog:
[ Zixing Liu ]