anon-vec lacks sufficient checks in public API

The following functions in the anon-vec crate are unsound due to insufficient checks on their arguments:: - AnonVec::getref - AnonVec::getmut - AnonVec::removeget The crate was built as a learning project and is not being maintained...

PT-2025-25491 · Crates.Io · Anon-Vec

The following functions in the anon-vec crate are unsound due to insufficient checks on their arguments:: - AnonVec::get ref - AnonVec::get mut - AnonVec::remove get The crate was built as a learning project and is not being maintained...

PT-2025-20009 · Crates.Io · Tanton Engine

The following functions in the tanton engine crate are unsound due to lack of sufficient boundary checks in public API: - Stack::offset - ThreadStack::get - RootMoveList::insert score depth - RootMoveList::insert score The tanton engine crate is no longer maintained, so there are no plans to...

xous has unsound usages of `core::slice::from_raw_parts`

We consider asslice and asslicemut unsound because: the pointer with any bit patterns could be cast to the slice of arbitrary types. The pointer could be created by unsafe new and deprecated fromparts. We consider that fromparts should be removed in latest version because it will help trigger...

RUSTSEC-2020-0009 `read_scalar` and `read_scalar_at` allow transmuting values without `unsafe` blocks

The readscalar and readscalarat functions are unsound because they allow transmuting values without unsafe blocks. The following example shows how to create a dangling reference: fn main deriveCopy, Clone, PartialEq, Debug struct S&'static str; impl flatbuffers::EndianScalar for S fn...