1.0.0 (current)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
1.0.0 (current)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
The current version of strck is 1.0.0.
0.1.2 (older version)
From mozilla/supply-chain copy of hg. By Makoto Kato.
This crate uses unsafe lock to keep invariant. I auditted code. Also, this doesn't have file access and network access.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
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…
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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 strck
. Alternatively, you can download the tarball of strck v1.0.0 or view the source online.
Reviewed in CL 685732460