indextree
cargo-geiger
indextree | cargo-geiger | |
---|---|---|
2 | 30 | |
593 | 1,327 | |
- | 2.3% | |
4.5 | 5.2 | |
about 2 months ago | 1 day ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
indextree
-
[Rust] À la recherche d'une caisse d'arbre (encore)
indextree - API horrible, pas de support supprimé
-
Hey Rustaceans! Got a question? Ask here! (17/2022)!
im looking at indextree atm: https://github.com/saschagrunert/indextree
cargo-geiger
-
Was Rust Worth It?
Instead of looking at the crates themselves, you might want to check your (or others') Rust application with https://github.com/rust-secure-code/cargo-geiger to get a sense of effective prevalence. I also dispute that the presence of unsafe somewhere in the dependency tree is an issue in itself, but that's a different discussion that many more had in other sub-threads.
-
Found a language in development called Vale which claims to be the safest AOT compiled language in the World (Claims to beSafer than Rust)
There's still plenty. Run cargo geiger on any of your projects and see for yourself.
-
Question Omnibus: Dependency Fingerprinting, Unsafe Rust, and Memory Safety
On point 2, the answer is cargo geiger, and judging how much memory safety you need for a given project.
- pliron: An extensible compiler IR framework, inspired by MLIR and written in safe Rust.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
How do you choose what crate you will use?
The amount of unsafe code is also a factor. cargo geiger is a handy tool for measuring it.
-
Seems legit
We have cargo-geiger that does just that.
-
Rosenpass – formally verified post-quantum WireGuard
For that, I believe you need to use cargo-geiger[0] and audit the results.
[0] - https://github.com/rust-secure-code/cargo-geiger
-
Hey Rustaceans! Got a question? Ask here (6/2023)!
cargo-geiger is a subcommand you can install which will check all the crates in your dependency graph for unsafe blocks and print out a report (which also shows if a crate has #![forbid(unsafe_code)] or not). You can then inspect those crates' sources to judge their use of unsafe for yourself. I don't think it has a "check" mode that simply errors if your dependency graph contains unsafe though, it's more about just collecting that information.
-
[CCS Proposal] Preliminary research on rewriting Monero node in Rust
wrt to memory safety, keep in mind that many rust crates use "unsafe" internally. There are tools available that can find these such as cargo-geiger. So I would suggest to avoid unsafe deps as much as possible. Since they cannot be avoided entirely, it is a good idea to keep a list of unsafe deps.
What are some alternatives?
book - The Rust Programming Language
bacon - background rust code check
rust-forest - Various implementation strategies for “DOM-like” tree data structures in Rust.
ziglings - Learn the Zig programming language by fixing tiny broken programs.
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
mold - Mold: A Modern Linker 🦠
miri - An interpreter for Rust's mid-level intermediate representation
orz - a high performance, general purpose data compressor written in the crab-lang
dlfile - For dl the file
pliron - Programming Languages Intermediate Representation
bstr - A string type for Rust that is not required to be valid UTF-8.
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio