This project contains known security vulnerabilities. Find detailed information at the bottom.
gstreamer(17 total, 8 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bitflags | ^1.0 | 1.2.1 | up to date |
| cfg-if | ^0.1 | 1.0.0 | out of date |
| futures-channel | ^0.3 | 0.3.13 | up to date |
| futures-core | ^0.3 | 0.3.13 | up to date |
| futures-util | ^0.3 | 0.3.13 | insecure |
| glib | ^0.9 | 0.10.3 | out of date |
| glib-sys | ^0.9 | 0.10.1 | out of date |
| gobject-sys | ^0.9 | 0.10.0 | out of date |
| gstreamer-sys | ^0.8 | 0.9.1 | out of date |
| lazy_static | ^1.0 | 1.4.0 | up to date |
| libc | ^0.2 | 0.2.87 | up to date |
| muldiv | ^0.2 | 1.0.0 | out of date |
| num-rational | ^0.2 | 0.3.2 | out of date |
| paste | ^0.1 | 1.0.4 | out of date |
| serde | ^1.0 | 1.0.123 | up to date |
| serde_bytes | ^0.11 | 0.11.5 | up to date |
| serde_derive | ^1.0 | 1.0.123 | up to date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-executor | ^0.3.1 | 0.3.13 | up to date |
| ron | ^0.5 | 0.6.4 | out of date |
| serde_json | ^1.0 | 1.0.64 | up to date |
futures-util: MutexGuard::map can cause a data race in safe codeAffected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.
This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.
The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData<&'a mut U> marker to the MappedMutexGuard type to tell the compiler that the guard is over
U too.