You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update ctutils and clipboard-win to clear cargo deny advisories - #110
cargo deny check failed on main: RUSTSEC-2026-0385 (ctutils 0.4.3, pulled in via digest → secret-service) and yanked clipboard-win 5.4.1 (via arboard). Fixed releases exist, so this is cargo update -p ctutils -p clipboard-win (→ 0.4.6 and 5.4.3). Lockfile only: no deny.toml ignore, no dependency trimmed, no source change.
Cross-review: approved (posted as a comment because author and reviewer share one account). Reviewed head 00e6358.
Lock diff.git diff origin/main...pr110 -- Cargo.lock changes exactly two packages: ctutils 0.4.3 → 0.4.6 and clipboard-win 5.4.1 → 5.4.3. Only the version and checksum lines change. No dependency lists change and nothing else gets bumped. The only other file is the progress file.
Versions are genuine. I checked the crates.io API: ctutils 0.4.6 was published 2026-10-25 and clipboard-win 5.4.3 on 2026-10-23. Neither is yanked, and both checksums match the ones in the lock file byte for byte. clipboard-win 5.4.1 (and 5.2.0–5.4.0) are yanked, which confirms the reason for the bump.
Advisory fixed. The local advisory-db copy of RUSTSEC-2026-0385 says patched = [">= 0.4.4"] (upstream RustCrypto/utils#1569), so 0.4.6 is covered.
Main fails, PR passes.
origin/main (92b8474): cargo deny check exits 1 with advisories FAILED (error[vulnerability] RUSTSEC-2026-0385 on ctutils 0.4.3 via digest 0.11.3 → hkdf → secret-service, plus error[yanked] on clipboard-win 5.4.1 via arboard → egui-winit). Bans, licenses and sources were ok.
PR head: cargo fmt --check && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace && cargo deny check exits 0. Tests: 1135 + 560 + 54 + 29 passed and 0 failed (1778 in total), which matches the progress file. Output: advisories ok, bans ok, licenses ok, sources ok.
No deny.toml change and no suppressions. This is the smallest honest fix. CI on all 3 systems was still running when I posted this, so the merge waits for it to go green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Davy · project thread
What
cargo deny checkfailed on main: RUSTSEC-2026-0385 (ctutils0.4.3, pulled in via digest → secret-service) and yankedclipboard-win5.4.1 (via arboard). Fixed releases exist, so this iscargo update -p ctutils -p clipboard-win(→ 0.4.6 and 5.4.3). Lockfile only: nodeny.tomlignore, no dependency trimmed, no source change.Verified (exit 0)
cargo fmt --checkcargo clippy --workspace --all-targets -- -D warningscargo test --workspace(1135 + 560 + 54 + 29 passed, 0 failed)cargo deny check(advisories, bans, licenses, sources ok)Progress file:
docs/progress/2026-10-26-cargo-deny-advisories.md.Generated by Claude Code