Repository navigation
ci: ignore RUSTSEC-2024-0449 (unsafe-libyaml unmaintained) until #53 - #54
Merged
Merged
Conversation
RustSec marked unsafe-libyaml unmaintained on 2026-10-12, which fails cargo deny on main. provio pulls it in through serde_yaml 0.9. The notice is not a vulnerability and has no patched version; the migration off serde_yaml is tracked in #53. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017bQP5nwJVPMXqMhewzhQv5 Signed-off-by: Bhaskar Gurram <gurrambhaskar.ai@gmail.com>
proofcheck:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cargo deny checkhas failed onmainsince RustSec published RUSTSEC-2024-0449 on 2026-10-12, an "unmaintained" notice forunsafe-libyaml, which provio pulls in throughserde_yaml0.9. It's a required check, so it blocks every PR.This adds a scoped ignore for that one advisory, with the reason and a link to #53, which tracks moving off
serde_yaml. The notice isn't a vulnerability and has no patched version. Nothing else indeny.tomlchanges.I checked
Cargo.lockagainst the current advisory database: this is the only advisory that affects provio's 323 registry dependencies.🤖 Generated with Claude Code
https://claude.ai/code/session_017bQP5nwJVPMXqMhewzhQv5
Generated by Claude Code