Cryptographically verifiable, distributed dependency reviews
Add the last reviewed version to Cargo.toml / [dependencies]:
bitflags = "1.3.2"Please, use mobile in landscape.
Filter reviews clicking on the numbers in the summary.
Full column names in tooltip hints: rating Negative, rating Neutral, rating Positive, rating Strong, thoroughness, understanding, reviews count.
bitflags code is a big macro. no dependency.
It looks basic and low. It has a lot of contributors.
I trust them to spot any strangeness.
malicious potential: 0%
build.rs: just check the rustc_minor_version
dependencies:0
macro_rules:6 (that is the point of the crate)
NONE: unsafe, FFI, asm!, file-read, file-write, no_mangle, network-access, proc_macro, process::command,
published to crates.io by: KodrAus (unknown to me)
Besides some macros manipulating attributes, the code is pretty straigtforward and benefits from a huge amount of tests
There's only one meaningful change since 1.3.1: non-snake-case names are
allowed in generated structs. My previous review stands.
There's only one meaningful change since 1.3.1: non-snake-case names are
allowed in generated structs. My previous review stands.
bitflags code is a big macro. no dependency.
It looks basic and low. It has a lot of contributors.
I trust them to spot any strangeness.
malicious potential: 0%
build.rs: just check the rustc_minor_version
dependencies:0
macro_rules:6 (that is the point of the crate)
NONE: unsafe, FFI, asm!, file-read, file-write, no_mangle, network-access, proc_macro, process::command,
published to crates.io by: KodrAus (unknown to me)
bitflags is a set of macros. They all look clean and correct. I flipped
through the tests too, and although I didn't pay as much attention, they too
look good — there are certainly more of them than of macros themselves, so
I'm quite confident about them. The docs are good too.
bitflags is a set of macros. They all look clean and correct. I flipped
through the tests too, and although I didn't pay as much attention, they too
look good — there are certainly more of them than of macros themselves, so
I'm quite confident about them. The docs are good too.
bitflags code is a big macro. no dependency.
It looks basic and low. It has a lot of contributors.
I trust them to spot any strangeness.
malicious potential: 0%
build.rs: just check the rustc_minor_version
dependencies:0
macro_rules:6 (that is the point of the crate)
NONE: unsafe, FFI, asm!, file-read, file-write, no_mangle, network-access, proc_macro, process::command,
published to crates.io by: KodrAus (unknown to me)
bitflags code is a big macro. no dependency.
It looks basic and low. It has a lot of contributors.
I trust them to spot any strangeness.
malicious potential: 0%
build.rs: just check the rustc_minor_version
dependencies:0
macro_rules:6 (that is the point of the crate)
NONE: unsafe, FFI, asm!, file-read, file-write, no_mangle, network-access, proc_macro, process::command,
published to crates.io by: KodrAus (unknown to me)
bitflags code is a big macro. no dependency.
It looks basic and low. It has a lot of contributors.
I trust them to spot any strangeness.
malicious potential: 0%
build.rs: just check the rustc_minor_version
dependencies:0
macro_rules:6 (that is the point of the crate)
NONE: unsafe, FFI, asm!, file-read, file-write, no_mangle, network-access, proc_macro, process::command,
published to crates.io by: KodrAus (unknown to me)
© bestia.dev 2023, MIT License, Version: 2023.608.1636
Open source repository for this web app: https://github.com/bestia-dev/cargo_crev_web/
simple macro