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.
near-chain-configs(14 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.62 | 1.0.86 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| derive_more | ^0.99.9 | 0.99.17 | up to date |
| near-config-utils | ^0.16.1 | 0.22.0 | out of date |
| near-crypto | ^0.16.1 | 0.22.0 | out of date |
| near-o11y | ^0.16.1 | 0.22.0 | out of date |
| near-primitives | ^0.16.1 | 0.22.0 | out of date |
| num-rational | ^0.3.1 | 0.4.2 | out of date |
| once_cell | ^1.13.1 | 1.19.0 | up to date |
| serde | ^1.0.136 | 1.0.202 | up to date |
| serde_json | ^1.0.68 | 1.0.117 | up to date |
| sha2 | ^0.10 | 0.10.8 | up to date |
| smart-default | ^0.6 | 0.7.1 | out of date |
| tracing | ^0.1.36 | 0.1.40 | 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.