RUSTSEC-2022-0054
(unmaintained)
on 2022-05-11: wee_alloc is Unmaintained
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.4.5 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- unknown
-
May have been packaged automatically without a review
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository with a git tag matching the version. 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 wee_alloc. Alternatively, you can download the tarball of wee_alloc v0.4.5 or view the source online.
Two of the maintainers have indicated that the crate may not be maintained.
The crate has open issues including memory leaks and may not be suitable for production use.
It may be best to switch to the default Rust standard allocator on wasm32 targets.
Last release seems to have been three years ago.
Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
Honorable Mention(s)
The below may serve to educate on potential future alternatives:
https://www.reddit.com/r/rust/comments/x1cle0/dont_use_wee_alloc_in_production_code_targeting/
https://github.com/rustwasm/wee_alloc/issues/85
https://github.com/rustwasm/wee_alloc/issues/106
GHSA-rc23-xxgq-x27g