nodo
grapl
Our great sponsors
| nodo | grapl | |
|---|---|---|
| 4 | 8 | |
| 17 | 671 | |
| - | - | |
| 6.8 | 9.8 | |
| 17 days ago | over 1 year ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
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.
nodo
-
Not allowed to use 3rd party code
Oh, certainly. One of the projects I really need to get back to has a hand-rolled argument parser because it's security critical and its needs are so simple and specialized.
-
Compiling in chroot? (for security)
(The repo is here if you want to subscribe for notification of updates when I get back to it.)
-
NPM malware and what it could imply for Cargo
It's using the placeholder name nodo (like "superuser do", but "you no do") and it's currently at https://github.com/ssokolow/nodo
-
Backdooring Rust crates for fun and profit
OK. It's at https://github.com/ssokolow/nodo/issues/1 until I come up with a non-placeholder name.
grapl
-
Rust – Faster compilation with the parallel front-end in nightly
https://github.com/grapl-security/grapl/
I just did a clean build `cargo build`, 19 minutes 44 seconds.
I added 1 line (`dbg!("foo")`) and it took 14.76s
-
Introduction to Curp Protocol
Awesome. So, CURP was pretty inspiring for the work I did on Grapl. Grapl Schemas had to define conflict resolution algorithms.
https://github.com/grapl-security/grapl/blob/main/etc/exampl...
As you can see here, there are some special built-ins that aren't important (keys, timestamps) but you can see there's @immutable (FWW) and @increment_only.
This meant that our graphs formed a big CRDT, which meant that every operation commuted, which meant that we could do weird things with our consensus. Reads could happen on stale data, writes could be dropped, we could read from two inconsistent databases and resolve the inconsistency in memory, etc. I even hacked this into ScyllaDB by encoding each merge function into an integer, and setting that as the TIMESTAMP, for when replication merging happened to the values - this meant we could perform writes (repeatedly) without reading a value first, and with no coordination between nodes. What I didn't have was a native solution that could take advantage of these constraints.
As you can tell, this project is obviously very interesting to me. I ran through this pretty quickly but I'll dig in more soon. I'm just excited to see this.
- Transitioning to Rust as a company
- Rust for cyber security
-
Why Rust is a great choice for startups
Rust, Python and Go. Props to you for being sensible with technology choice.
-
Is Rust Web Yet?
That's great for you and your team, but looking at https://github.com/grapl-security/grapl it seems like your needs are pretty different from most web developers.
- NPM malware and what it could imply for Cargo
What are some alternatives?
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
ntex - framework for composable networking services
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
cap-std - Capability-oriented version of the Rust standard library
demo-rust-axum - Demo of Rust and axum web framework with Tokio, Tower, Hyper, Serde
watt - Runtime for executing procedural macros as WebAssembly
rfcs - RFCs for changes to Rust
wg - Coordination repository for the Secure Code Working Group
rust-wiki-backup - A backup of the Rust wiki
crates.io - The Rust package registry
cargo2nix - Granular builds of Rust projects for Nix