This project contains known security vulnerabilities. Find detailed information at the bottom.
flume(4 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-core | ^0.3.5 | 0.3.34 | up to date |
| futures-sink | ^0.3.5 | 0.3.34 | up to date |
| nanorand ⚠️ | ^0.4 | 0.8.0 | insecure |
| spinning_top | ^0.2 | 0.3.0 | out of date |
(7 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.5 | 1.13.2 | up to date |
| criterion | ^0.3.1 | 0.8.2 | out of date |
| crossbeam-channel | ^0.4 | 0.5.17 | out of date |
| crossbeam-utils | ^0.7 | 0.8.23 | out of date |
| futures | ^0.3 | 0.3.34 | up to date |
| rand | ^0.7 | 0.10.3 | out of date |
| waker-fn | ^1.1.0 | 1.2.0 | up to date |
nanorand: nanorand 0.5.0 - RNGs failed to generate properly for non-64-bit numbersIn versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could
fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just
an as conversion.
This often manifested as RNGs returning nothing but 0, including the cryptographically secure ChaCha random
number generator..