This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
fac(15 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2.0 | 0.2.14 | up to date |
| bigbro | ^0.5 | 0.5.2 | up to date |
| clap | ^2.33.0 | 4.5.4 | out of date |
| crude-profiler | ^0.1.7 | 0.1.7 | up to date |
| ctrlc | ^3.0 | 3.4.4 | up to date |
| git-version | ^0.3.4 | 0.3.9 | up to date |
| internment ⚠️ | ^0.3.12 | 0.8.2 | out of date |
| lazy_static | ^1.4.0 | 1.4.0 | up to date |
| libc | ^0.2 | 0.2.153 | up to date |
| metrohash | ^1.0.1 | 1.0.6 | up to date |
| notify | ^4.0.1 | 6.1.1 | out of date |
| num_cpus | ^1.5.0 | 1.16.0 | up to date |
| pathdiff | ^0.1.0 | 0.2.1 | out of date |
| termcolor | ^1.0.5 | 1.4.1 | up to date |
| tinyset | ^0.4.1 | 0.4.15 | up to date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| quickcheck | ^0.9.0 | 1.0.3 | out of date |
internment: Use after free in ArcIntern::dropArcIntern::drop has a race condition where it can release memory
which is about to get another user. The new user will get a reference
to freed memory.
This was fixed by serializing access to an interned object while it is being deallocated.
Versions prior to 0.3.12 used stronger locking which avoided the problem.
internment: Intern<T>: Data race allowed on TAffected versions of this crate unconditionally implements Sync for Intern<T>.
This allows users to create data race on T: !Sync, which may lead to undefined behavior
(for example, memory corruption).
The flaw was corrected in commit 2928a87 by adding the trait bound T: Sync in the Sync impl of Intern<T>.