Deps.rs

krankerl 0.10.0

[![dependency status](https://deps.rs/crate/krankerl/0.10.0/status.svg)](https://deps.rs/crate/krankerl/0.10.0)

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 krankerl

Dependencies

(23 total, 14 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.100.22.1out of date
 composer^0.10.2.1out of date
 docopt^1.01.1.1up to date
 failure^0.1.30.1.8up to date
 flate2^1.01.1.9up to date
 futures^0.10.3.32out of date
 git2^0.70.20.4out of date
 globset^0.4.20.4.18up to date
 hex^0.30.4.3out of date
 indicatif^0.9.00.18.4out of date
 nextcloud_appinfo^0.4.10.6.0out of date
 nextcloud_appsignature^0.3.00.7.1out of date
 nextcloud_appstore^0.4.00.8.0out of date
 npm_scripts^0.1.20.2.0out of date
 pathdiff^0.1.00.2.3out of date
 serde^1.01.0.228up to date
 serde_derive^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 tar ⚠️^0.4.200.4.45maybe insecure
 tokio ⚠️^0.1.111.50.0out of date
 toml^0.4.81.1.2+spec-1.1.0out of date
 walkdir^2.2.72.5.0up to date
 xdg^2.1.03.0.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 fs_extra^1.1.01.3.0up to date
 tempdir^0.30.3.7up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

tar: `unpack_in` can chmod arbitrary directories by following symlinks

RUSTSEC-2026-0067

In versions 0.4.44 and below of tar-rs, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root.

This issue has been fixed in version 0.4.45.

tar: tar-rs incorrectly ignores PAX size headers if header size is nonzero

RUSTSEC-2026-0068

Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX size header in cases where the base header size is nonzero.

As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue.

Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size — other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers.

This issue has been fixed in version 0.4.45.