Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deny.toml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ ignore = [
{ id = "RUSTSEC-2026-0194", reason = "`quick-xml` <0.41 pulled transitively via object_store (datafusion) and reqsign-aws-v4 (opendal); upstream must upgrade first" },
{ id = "RUSTSEC-2026-0195", reason = "`quick-xml` <0.41 pulled transitively via object_store (datafusion) and reqsign-aws-v4 (opendal); upstream must upgrade first" },
{ id = "RUSTSEC-2024-0449", reason = "`serde_yaml` pulled transitively via datafusion-substrait; serde features not utilized by us" },
]
{ crate = "chacha20@0.10.0", reason = "yanked upstream; pulled transitively via rand -> object_store, no newer version to update to yet, yanking was for UB in SSE2 which we don't really support anyways" },]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

chacha20 0.10.2 is already published and unyanked, and RustCrypto/stream-ciphers#580 fixes the SSE4.1 intrinsic used by the SSE2 RNG backend. The locked rand 0.10.1 accepts chacha20 ^0.10.0, so this update does not require a new rand or object_store release. Consider refreshing the root, Python, and JNI lockfiles to that version instead of suppressing the warning. This is non-blocking for this revision because the runtime dependency and its exposure are unchanged.

# If this is true, then cargo deny will use the git executable to fetch advisory database.
# If this is false, then it uses a built-in git library.
# Setting this to true can be helpful if you have special authentication requirements that cargo-deny does not support.
Expand Down
Loading