Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
goblin
-
[ANN] yabridge 4.0, with chainloading, an overhauled backend, and many user experience improvements
On the backend side, a lot has changed. The biggest change is that the dependency on Boost has been completely removed, and everything has been reworked accordingly. This should make packaging easier, as yabridge now no longer depends on any system library other than the basic libraries needed to interact with X11. Some parts of Boost have been replaced by other headers-only libraries, while other parts now simply use custom implementations. All of this is explained in more detail in the 'Packaging notes' section of the changelog. Yabridgectl also lost its dependency on winedump, at least in most cases. It now tries to parse plugin libraries directly using the goblin binary parsing library. This should also speed up the syncing process. I did, however, run into one plugin that this new parser couldn't handle. If that happens then winedump will still be used instead.
-
Crash reporting in Rust
For now the minidump creation is a fairly faithful port of the Breakpad code, but like I said some of that code is really old, so there's probably cases where taking a step back and rethinking the approach based on new kernel or OS capabilities or, instead of recreating process snapshotting for each non-Windows, just have a really good parser for each OSes crash format that does a transform. Rust is a fantastic language for writing those kinds of parsers, so that would definitely be an interesting avenue to investigate, especially since in the Linux case a lot of groundwork has already been done by goblin.
-
What's your favourite under-rated Rust crate and why?
I do security-related projects in Rust, and goblin has been my go-to crate for any type of binary parsing (ELF/PE/Mach-O).
enum-map
-
(Tip of my fingers) Library with a macro to create an enum from a range
I know I could write (and have written) this enum myself by hand. I don't want to use a newtype around u8 or something like that because I want the static guarantees of an enum — plus I'm using EnumMap to create statically-allocated maps with enum keys, so I'm hoping whatever this library was will play nicely with it.
-
Is std::collections::HashMap optimized for enums?
What you might want is enum-map instead.
-
What's your favourite under-rated Rust crate and why?
enum_map is great for dense maps where the keys are the variants of a discriminant-only enum.
What are some alternatives?
pwninit - pwninit - automate starting binary exploit challenges
strum - A small rust library for adding custom derives to enums
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
parse-size - Parse byte size into integer accurately.
eve-echoes-tools - Collection of tools helping in reverse engineering Eve Echoes
structopt - Parse command line arguments by defining a struct.
LIEF - LIEF - Library to Instrument Executable Formats
serde-plain - A serde serializer that serializes a subset of types into plain strings
binary-security-check - Moved: https://codeberg.org/koutheir/binary-security-check
actix-web-static-files - actix-web static files as resources support
netease-messiah-tools - Tools working with files in NetEase's Messiah Engine (Primarily aimed towards Diablo Immortal for now)
NumToA - An efficient method of heaplessly converting numbers into their string representations, storing the representation within a reusable byte array.