chacha20 0.10.1 is yanked, reached via rand 0.10.2 #23
Labels
No labels
waiting-on-julian
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jlxq0/carddav-mcp#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cargo auditreports one allowed warning as of 2026-08-28:No RustSec advisory, so
cargo auditexits 0 and CI passes. It appeared betweentwo audit runs a few hours apart on the same lockfile, which is the pitfall
AGENTS.mdalready records about rerunning against the finished lockfile.Two dependency paths,
rmcpandreqwest, so clearing it means both bring arandthat no longer pulls a yankedchacha20. Deliberately not pulled ontothe
v0.1.5outage fix.Not urgent: a yanked crate is a publishing-side signal, not a vulnerability, and
nothing here is known to be exploitable. Worth clearing on the next routine
dependency pass so a real advisory is not mistaken for this line.