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.

Crate cargo-tarpaulin

Dependencies

(29 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cargo_metadata^0.200.22.0out of date
 cfg-if^1.0.11.0.3up to date
 chrono ⚠️^0.40.4.41maybe insecure
 clap^4.4.04.5.46up to date
 coveralls-api^0.7.00.7.0up to date
 gimli^0.32.00.32.2up to date
 git2^0.200.20.2up to date
 glob^0.3.20.3.3up to date
 humantime-serde^11.1.1up to date
 indexmap~1.82.11.0out of date
 lazy_static^1.51.5.0up to date
 libc^0.2.1740.2.175up to date
 llvm_profparser^0.8.30.8.3up to date
 nix^0.30.10.30.1up to date
 num_cpus^1.17.01.17.0up to date
 object^0.370.37.3up to date
 proc-macro2^1.01.0.101up to date
 procfs^0.170.18.0out of date
 quick-xml^0.370.38.3out of date
 quote^1.01.0.40up to date
 regex^1.111.11.2up to date
 rustc-demangle^0.1.250.1.26up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.143up to date
 syn^2.02.0.106up to date
 toml^0.80.9.5out of date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.3.190.3.20up to date
 walkdir^2.5.02.5.0up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 lcov^0.8.10.8.1up to date
 rusty-fork^0.3.00.3.0up to date
 test-log^0.2.170.2.18up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References