Exposes reference to non-Sync data to an arbitrary thread

openssl X509NameBuilder::build returned object is not thread safe

MsQueue push/pop use the wrong orderings

Delegate functions are missing Send bound

Data race when sending and receiving after closing a oneshot channel

AtomicBucket unconditionally implements Send/Sync

MutexGuard<Cell<i32>> must not be Sync

Insufficient synchronization in Arc::get_mut

RingBuffer can create multiple mutable references and cause data races

Data race and memory safety issue in Index

Intern: Data race allowed on T

Queues allow non-Send types to be sent to other threads, allowing data races

MvccRwLock allows data races & aliasing violations

Send/Sync bound needed on T for Send/Sync impl of RcuCell

ReaderResult should be bounded by Sync

SyncChannel can move 'T: !Send' to other threads

Shared can cause a data race

ShmWriter allows sending non-Send type across threads

AtomicBox lacks bound on its Send and Sync traits allowing data races

Queue should have a Send bound on its Send/Sync traits

LockWeak<T> allows to create data race to T.

Slock allows sending non-Send types across thread boundaries

SyncRef's clone() and debug() allow data races

CopyCell lacks bounds on its Send trait allowing for data races

Bunch unconditionally implements Send/Sync

Cache: Send/Sync impls needs trait bounds on K

ArcGuard's Send and Sync should have bounds on RC

dces' World type can cause data races

convec::ConVec unconditionally implements Send/Sync

beef::Cow lacks a Sync bound on its Send trait allowing for data races

ReadTicket and WriteTicket should only be sendable when T is Send

AtomicBox implements Send/Sync for any T: Sized

Decoder<R> can carry R: !Send to other threads

QueueSender/QueueReceiver: Send/Sync impls need T: Send

PinSlab and Unordered<T, S> need bounds on their Send/Sync traits

Future lacks bounds on Send and Sync.

Singleton lacks bounds on Send and Sync.

Demuxer can carry non-Send types across thread boundaries

AtomicOption should have Send + Sync bound on its type argument.

conquer-once's OnceCell lacks Send bound for its Sync trait.

hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.

ButtplugFutureStateShared allows data race to (!Send|!Sync) objects

may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.

Soundness issue: Input can be misused to create data race to an object

LateStatic has incorrect Sync bound

Queues allow non-Send types to be sent to other threads, allowing data races

ImageChunkMut needs bounds on its Send and Sync traits

Aovec lacks bound on its Send and Sync traits allowing data races

TreeFocus lacks bounds on its Send and Sync traits

Soundness issue with base::Error

UsbContext trait did not require implementers to be Send and Sync.

Unsound: can make ARefss contain a !Send, !Sync object.

Send/Sync bound needed on V in impl Send/Sync for ARCache<K, V>

Thex allows data races of non-Send types across threads

MPMCConsumer/Producer allows sending non-Send type across threads

TryMutex allows sending non-Send type across threads

GenericMutexGuard allows data races of non-Sync types across threads

Some lock_api lock guard objects can cause data races

Improper Sync implementation on FuturesUnordered in futures-utils can cause data corruption

MutexGuard::map can cause a data race in safe code

Multiple security issues including data race, buffer overflow, and uninitialized memory drop

Unsafe Send implementation in Atom allows data races