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
We could be pulling data from https://github.com/RustSec/advisory-db and displaying it somewhere, maybe similar to the yanked warnings, to improve broadcasting of known security issues to potentially impacted users.
This might not be possible because the advisory db is maintained outside the Rust Project, unless its links through wg-secure-code make it official enough.
The text was updated successfully, but these errors were encountered:
I feel like it's more likely for someone to be looking at docs for a crate that they're already using than going to that crate's crates.io page. It's something that should probably be displayed in both locations really.
Thinking about it more this is probably something that needs wider discussion, and really would be best to integrate in both crates.io and docs.rs, so I'll bring up docs.rs on the more upstream issue rust-secure-code/wg#16 in case that makes it to RFC at some point (and at least now we have an issue search result for "advisory" to follow 😁).
We could be pulling data from https://github.com/RustSec/advisory-db and displaying it somewhere, maybe similar to the yanked warnings, to improve broadcasting of known security issues to potentially impacted users.
This might not be possible because the advisory db is maintained outside the Rust Project, unless its links through wg-secure-code make it official enough.
The text was updated successfully, but these errors were encountered: