-
Couldn't load subscription status.
- Fork 1.6k
Adding a crates.io Security tab #3872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
8017e12 to
0202b53
Compare
0202b53 to
80e534c
Compare
|
FYI while I'm a fan of force-pushing, I'd recommend against it for RFCs as the commits regularly get referenced. |
| are about the desirability of the feature, the implementation approach, and the governance | ||
| of the source data. | ||
|
|
||
| # Future possibilities |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reporting on provenance is related: https://lawngno.me/blog/2024/06/10/divine-provenance.html
The challenge there is setting the right tone of "there are divergences, this needs further investigation" rather than "this is bad!". Unsure if that can be satisfied on a Security tab, or if it needs to be a Health tab or maybe an Insights tab?
Yes, will stop doing so as I address feedback -- figured getting the RFC number in place was fine for force-pushing. |
Summary
This RFC proposes that crates.io should provide insight into vulnerabilities and unsound
API surface based on the RustSec advisory database.
Rendered