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.
rp2040-hal(24 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bitfield | ^0.14.0 | 0.15.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| cortex-m | ^0.7.2 | 0.7.7 | up to date |
| critical-section | ^1.0.0 | 1.1.2 | up to date |
| defmt | >=0.2.0, <0.4 | 0.3.8 | up to date |
| embedded-dma | ^0.2.0 | 0.2.0 | up to date |
| embedded-hal | ^0.2.5 | 1.0.0 | out of date |
| embedded-hal-async | ^1.0.0 | 1.0.0 | up to date |
| embedded-hal-nb | ^1.0.0 | 1.0.0 | up to date |
| embedded-io | ^0.6.1 | 0.6.1 | up to date |
| frunk | ^0.4.1 | 0.4.2 | up to date |
| fugit | ^0.3.6 | 0.3.7 | up to date |
| i2c-write-iter | ^1.0.0 | 1.0.0 | up to date |
| itertools | ^0.10.1 | 0.13.0 | out of date |
| nb | ^1.0 | 1.1.0 | up to date |
| paste | ^1.0 | 1.0.15 | up to date |
| pio | ^0.2.0 | 0.2.1 | up to date |
| rand_core | ^0.6.3 | 0.6.4 | up to date |
| rp2040-hal-macros | ^0.1.0 | 0.1.0 | up to date |
| rp2040-pac | ^0.6.0 | 0.6.0 | up to date |
| rtic-monotonic | ^1.0.0 | 1.0.0 | up to date |
| usb-device | ^0.3 | 0.3.2 | up to date |
| vcell | ^0.1 | 0.1.3 | up to date |
| void | ^1.0.2 | 1.0.2 | up to date |
(14 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cortex-m-rt | ^0.7 | 0.7.4 | up to date |
| cortex-m-rtic | ^1.1.4 | 1.1.4 | up to date |
| defmt | ^0.3 | 0.3.8 | up to date |
| defmt-rtt | ^0.4.0 | 0.4.1 | up to date |
| dht-sensor | ^0.2.1 | 0.2.1 | up to date |
| embedded-alloc | ^0.5.1 | 0.5.1 | up to date |
| futures | ^0.3.30 | 0.3.30 | up to date |
| hd44780-driver | ^0.4.0 | 0.4.0 | up to date |
| nostd_async | ^0.6.1 | 0.6.1 | up to date |
| panic-halt | ^0.2.0 | 0.2.0 | up to date |
| panic-probe | ^0.3.1 | 0.3.2 | up to date |
| pio-proc | ^0.2.0 | 0.2.2 | up to date |
| rand | ^0.8.5 | 0.8.5 | up to date |
| rp2040-boot2 | ^0.3.0 | 0.3.0 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.