Learn/Digital FreedomOpen Source

Remade With Rust Crates Break 120,000 Downloads

Remade with Rust crates just crossed 120,000 downloads — 124,230 on the counter. rusty_h264, rusty_alloc, and SpaceDB lead the pull.

Signed by M·
crates.io-style counter showing a purple download arrow and 124,230 Total Downloads on a light cream background

The counter is not a press release. It is a number on the registry: 124,230 total downloads across the Remade with Rust crates. That is past 120,000 — not a vanity milestone, a signal that builders are pulling memory-safe replacements into real Cargo.lock files.

Remade with Rust is MATA's program to rebuild the internet's load-bearing primitives in Rust — codecs, allocators, identity, storage — under permissive licenses on github.com/remade-with-rust. The thesis lives in The Importance of Remade With Rust and rebuilding the foundation of the internet. This article is the download story: why the Remade with Rust crates crossing 120,000 matters, and which three crates are doing most of the work — rusty_h264, rusty_alloc, and SpaceDB.

Why 120,000 Remade With Rust Crate Downloads Matter

Crate downloads are not likes. Each one is a resolve in someone's build: CI, a laptop, a mesh node, a WASM target. When Remade with Rust crates break 120,000, it means the program left the catalog page and entered dependency graphs. That is the only adoption metric that survives a marketing cycle.

Memory-safe rebuilds only win if people depend on them. A perfect rewrite that nobody links is a museum piece. The NIST Secure Software Development Framework pushes organizations toward memory-safe languages for a reason: the CVE class that never ages out of C parsers and allocators. Remade with Rust crate downloads are how that push shows up in Rust — one cargo add at a time.

Trust, Security, and Incentive sit under the number. Trust that the crate you pulled is the rebuild, not a binding to the old C heap. Security that whole exploit classes never compile. Incentive that MIT / Apache / BSD licensing lets a commercial product ship without a copyleft tax on the runtime. The Electronic Frontier Foundation has spent years on tools that stay open enough for individuals to inspect. Permissive Remade with Rust crates are that posture at the foundation layer.

One hundred twenty thousand is not "finished." It is proof of motion. The catalog still has experimental engines and pre-1.0 codecs. The downloads say the motion is already useful.

The Crates Leading Remade With Rust Downloads

Three crates dominate the story builders tell when they open the Remade with Rust portfolio: video that cannot stay in C, allocation that should not silently corrupt, and storage that does not assume a data center. Those are rusty_h264, rusty_alloc, and SpaceDB.

rusty_h264 Leads Remade With Rust Codec Downloads

H.264 is still the wire format of the everyday internet — video calls, cameras, browsers, game streams. The libraries everyone reaches for are x264 and openh264: large C/C++ codebases with a long CVE history in bitstream parsing and buffer handling. Every app that links them inherits that surface.

rusty_h264 is a clean-room pure-Rust rebuild with #![forbid(unsafe_code)] on the codec core — no C, no FFI. Bit-exact decode against ffmpeg across the QP range for Constrained Baseline today. BSD-2-Clause. That combination is why Remade with Rust crate downloads concentrate here: teams need H.264 and a memory-safe story they can put in a security review. When the Remade with Rust crates crossed 120,000, this codec was one of the main reasons the counter moved.

Edge and mesh products make the pull sharper. A decoder that needs a C toolchain fails the "no C on the node" test. rusty_h264 does not. See AI on the edge for how codecs sit under on-device perception — the download count is the same thesis measured in cargo resolves.

rusty_alloc Is The Remade With Rust Foundation Download

Every long-running process routes allocations through a general-purpose allocator. When that allocator is C and a double-free is silent, the bug shows up hours later somewhere else. rusty_alloc is a pure-Rust reimplementation of the mimalloc architecture — not a binding — with a deliberate behavioral change: a double free aborts instead of quietly corrupting the heap.

That is why builders download it even when they are not shipping a codec. It is the foundation Remade with Rust crates share: UI tokens, symbols, a11y helpers, and top-level binaries via rusty_alloc_default. One global allocator seam, whole workspace on the same heap. Remade with Rust crate downloads at 120,000+ include a lot of "we just needed a safer malloc" resolves — unglamorous, high leverage.

The Federal Trade Commission is not about allocators, but it is about products that fail silently and then claim they were fine. Aborting on double-free is the opposite habit: loud failure at the right layer.

SpaceDB Pulls Remade With Rust Storage Downloads

Firebase and Supabase assume a data center, an always-on network, and a round trip for every write. SpaceDB is the Remade with Rust answer for a world without that assumption: local-first, CRDT-native, mesh-replicated, encrypted app data near the users who own it. Vector search that stays local. Capability-based access. Dual Apache-2.0 OR MIT.

When Remade with Rust crates break 120,000 downloads, SpaceDB is part of the lead because builders are tired of renting a source of truth. RAG pipelines, wallets, and edge apps need a store that survives offline and partition. That is the Digital Freedom data layer in a crate name — and download counts are how you know people are trying it, not just reading the card.

What The Remade With Rust Download Milestone Means Next

A milestone is a checkpoint, not a finish line. The useful question is what the next hundred thousand Remade with Rust crate downloads should look like.

More Remade With Rust Crates In Production Graphs

The next step is not a bigger splash page. It is more Cargo.lock files that pin rusty_h264, rusty_alloc, SpaceDB, and the rest of the catalog in production CI. Deputy exists so those graphs can be vaulted and verified. Downloads without a supply-chain story are incomplete; downloads with a vault are how Remade with Rust crates stay trustworthy past the novelty phase.

Edge And WASM Keep Pulling Remade With Rust Downloads

WASM and edge targets cannot casually ship *-sys crates. Pure-Rust codecs and allocators are what make those targets honest. Products like RAG Converter and the skill folders on Dev Tools push the same stack into agent workflows and browser tabs. Expect Remade with Rust crate downloads to keep climbing wherever "no C toolchain" is a hard requirement.

Keep The Remade With Rust Catalog Honest

We will not pretend 120,000 means every crate is 1.0. Experimental engines stay labeled. Performance claims stay measured. The counter on the screenshot — 124,230 total downloads — is a fact. The work ahead is still the catalog: more codecs to parity, more engines off the experimental list, more SpaceDB deployments that prove the mesh.

If you came from Learn looking for whether Remade with Rust is real outside MATA's own apps, the registry answers: the Remade with Rust crates broke 120,000 downloads, and rusty_h264, rusty_alloc, and SpaceDB are why the number is not empty.