-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add trophy case to README #20
Comments
yes plz add the |
Here's what I think it could look like: libflateDiscovered and fixed a security issue plus 3 non-expoitable safety issues. Reduced number of unsafe blocks in the crate from 16 to 1, two of which were replaced with shared dependency crates. More info Or we could go for a more structured format, such as:
Thoughts? |
@oyvindln would you be OK with your recent work on miniz_oxide being showcased on this repository? |
that table format looks crazy bad on mobile display. Let's stick to paragraphs which will reflow to smaller screens easily. |
On the other hand I really like the structured presentation that provides an overview at a glance. https://github.com/rust-fuzz/trophy-case just goes down that route and doesn't care about mobile. Perhaps we could strike a middle ground with bullet points? How about this: libflate
Also discovered and fixed 3 non-expoitable safety issues. |
We should probably also credit the people who performed the audit. Attribution is important and also helps motivate contributors. |
@Shnatsel sure |
Added initial version in #23. Please add your contributions! |
It's important for collaborative projects to show progress, as it motivates further participation. To that end we should surface the crates already audited and/or cleansed in the README.
The text was updated successfully, but these errors were encountered: