* (all versions)
From EmbarkStudios/rust-ecosystem. By Embark on 2023-01-01.
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
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 crash-handler. Alternatively, you can download the tarball of crash-handler v0.6.2 or view the source online.
Maintained by Embark.
This crate contains a large amount of unsafe code as it is interacting with OS signal/exception handling functionality, but is fairly thoroughly tested. Note on Linux targets, this also performs an interposition of pthread_create.