-
Notifications
You must be signed in to change notification settings - Fork 10
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
crates.io RustSec Auditor #13
Comments
Will |
@alex yes, |
👍 -- wanted to confirm that checking crates.io was about being proactive vs. a first line of defense. |
https://gitlab.com/zachreizner/crates-audit/ implements checking crates.io index against RustSec advisory database and outputs the result in .json, .bin and .toml formats. It also has a web UI that displays this info. It flags crates with no semver-compatible upgrade path, i.e. the issues that cannot be resolved by running The tool is pretty much complete aside of a couple trivial issues I feel integrating this info into crates.io would prevent serious issues from being masked, like it happened in the amqp case. |
Hear hear @Shnatsel, crates-audit is really starting to shape up. Great work @zachreizner ! One thing I've been trying to facilitate is integrating RustPräzi, a crater-like tool which builds a complete call graph of all of crates.io: I added support for collecting the relevant metadata (paths to functions) to RustSec advisories. One of the authors of RustPräzi (@Inventitech) took a look at actually trying to consume it and we discovered some issues: It should be simple to address, though. |
Nice! Is there a repository with a prototype of the RustPrazi-based tool that I could link to? |
I'd suggest asking on their Gitter: https://gitter.im/praezi/rust |
The first milestone for this would be a program that cross-references the RustSec advisory-db with the crates.io database and prints crates with vulnerable dependencies.
The second milestone is notifying crates with vulnerable dependencies, so that they may upgrade.
The text was updated successfully, but these errors were encountered: