zyl71 opened a new issue, #3742:
URL: https://github.com/apache/iceberg-rust/issues/3742

   Hi, and thanks for maintaining this project.
   
   `.cargo/audit.toml` still ignores the advisory below. `Cargo.lock` on the 
default branch no longer holds a version of the affected crate inside the 
affected range, so the entry no longer suppresses anything and can be removed.
   
   | Advisory | Summary | In `Cargo.lock` now | Patched in | Severity |
   |---|---|---|---|---|
   | RUSTSEC-2026-0381 | Bundled root certificates allow trust in distrusted 
emSign intermediates | `webpki-roots` 0.26.11, 1.0.10 | 1.0.10 (0.26.11 is 
listed as unaffected) | not scored |
   
   RustSec marked `webpki-roots` 0.26.11 as unaffected on 2026-10-21, the day 
after the advisory was published: that release only re-exports the 1.x root 
list. Since then the advisory no longer matches the 0.26.11 entry in a lock 
file.
   
   What we checked on 2026-11-21, on the default branch at commit 
`219078c9d8d8`, by reading public files only:
   
   - The id is on an active (non-comment) line of the file.
   - No version of the crate in `Cargo.lock` is inside the affected range of 
the advisory.
   
   Why it is worth removing: an ignore entry keeps muting the advisory id for 
as long as it stays in the file. If the crate were later pinned back to an 
affected version, cargo-audit would stay silent about it.
   
   Disclosure: the check and this text were produced with automated tooling, 
including an LLM. The repository files were re-read from the default branch on 
2026-11-21.
   
   Feel free to close this if it is not useful.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to