ferrous-systems / cargo-review-deps
A tool for auditing Cargo dependencies during updates
☆54Updated 6 years ago
Alternatives and similar repositories for cargo-review-deps:
Users that are interested in cargo-review-deps are comparing it to the libraries listed below
- ☆64Updated 4 years ago
- A simple helper to transform Markdown links to intra-doc links in Rust projects when appropriate.☆36Updated 4 years ago
- "Freedom from syn": Proc macro tools for operating on token trees☆107Updated 4 years ago
- Spawn processes with arbitrary closures in rust☆109Updated 3 years ago
- ☆54Updated 3 years ago
- A Cargo plugin to list unsafe code in a Rust project.☆43Updated 6 years ago
- Rust serializer library☆86Updated 9 months ago
- ☆58Updated 5 months ago
- ☆60Updated 7 years ago
- A proc-macro that checks if blockers (issues) have been resolved.☆35Updated 4 years ago
- Generate a Markdown section in your README based on your Rust documentation☆58Updated 2 years ago
- Safely combine results☆81Updated 4 months ago
- Proc macro for using doc comments as context for errors/logs/profiling/whatever via `tracing`☆45Updated 2 years ago
- Pluralization handling in Rust☆36Updated 2 years ago
- To futures-lite as futures-lite is to futures: smaller.☆53Updated last month
- Find calls to panic functions in rust executables☆35Updated 3 years ago
- Asynchronous byte buffers and pipes for concurrent I/O programming.☆99Updated last year
- Machine scalar casting that meets your expectations☆74Updated 3 years ago
- Set the error context using doc comments☆53Updated 5 years ago
- Streamline updating a Tokio 0.1 application to Tokio 0.2.☆51Updated 4 years ago
- A data serialization format as similar as possible to Rust's own syntax☆43Updated 2 years ago
- ☆55Updated 7 months ago
- Rust crate to use process file descriptors (pidfd) for Linux☆45Updated 10 months ago
- A lightweight, no-std, object-safe, serialization-only framework for Rust☆95Updated 2 weeks ago
- Procedural macro span debugger/visualizer☆40Updated 4 years ago
- Utility for reusing memory☆52Updated 5 years ago
- Find the load at which a benchmark falls over.☆35Updated 4 years ago
- A `#[safe]` attribute for explaining why `unsafe { ... }` is OK.☆81Updated 5 years ago
- failure + error-chain = 💖☆54Updated 3 years ago
- Opentelemetry layer for the tracing crate☆23Updated 4 years ago