0.1.2 (current)
From mozilla/supply-chain copy of hg. By Henri Sivonen.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.1.2 ed8a4c — diff review from 0.1.2 only (current)
From mozilla/supply-chain copy of hg. Audited without comment by Bobby Holley.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
Implied by other criteria
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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 chardetng_c. Alternatively, you can download the tarball of chardetng_c v0.1.2 or view the source online.
I, Henri Sivonen, wrote this crate for Gecko even though it is published via crates.io. The buffer input assumes Rust slice constraints for the start pointer. In Gecko, this is taken care of by mozilla::Span, but the C API doesn't conform to idiomatic C constraints on this point.