This project contains known security vulnerabilities. Find detailed information at the bottom.
vega_lite_3(10 total, 4 outdated, 1 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.22 | 1.0.82 | up to date |
| csv | ^1.1 | 1.3.0 | up to date |
| derive_builder | ^0.9.0 | 0.20.0 | out of date |
| derive_more | ^0.99 | 0.99.17 | up to date |
| nalgebra ⚠️ | ^0.19.0 | 0.32.5 | out of date |
| ndarray | ^0.13 | 0.15.6 | out of date |
| rulinalg ⚠️ | ^0.4.2 | 0.4.2 | insecure |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| showata | ^0.2.0 | 0.3.2 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| csv | ^1.1 | 1.3.0 | up to date |
| ndarray-rand | ^0.11 | 0.14.0 | out of date |
rulinalg: Lifetime boundary for `raw_slice` and `raw_slice_mut` are incorrectThe affected version of rulinalg has incorrect lifetime boundary definitions
for RowMut::raw_slice and RowMut::raw_slice_mut. They do not conform with
Rust's borrowing rule and allows the user to create multiple mutable references
to the same location. This may result in unexpected calculation result and data
race if both references are used at the same time.
nalgebra: VecStorage Deserialize Allows Violation of Length InvariantThe Deserialize implementation for VecStorage did not maintain the invariant that the number of elements must equal nrows * ncols. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.
This flaw was introduced in v0.11.0 (086e6e) due to the addition of an automatically derived implementation of Deserialize for MatrixVec. MatrixVec was later renamed to VecStorage in v0.16.13 (0f66403) and continued to use the automatically derived implementation of Deserialize.
This flaw was corrected in commit 5bff536 by returning an error during deserialization if the number of elements does not exactly match the expected size.