TL;DR: The FAF ecosystem just crossed 60,000 downloads. 27 days after 50k. The Mar → Apr jump alone is +24k — the biggest calendar month on the chart. Same 16 packages. Same 3 registries. Same zero marketing budget. The format keeps spreading because the format keeps working.
The Numbers
The Packages
npm
PyPI
crates.io
From 50k to 60k
Twenty-seven days. Here's what shipped:
- /slash — Token optimization for context engineers. 4.8 KB WASM. Routes, evaluates, aborts. Saved $477 in a day.
- RadioFAF Episodes 12–15 — The Token Tax, Nelly Wants to Sing, Nelly Tries to Rap, Grok Unfiltered. Live AI radio, every episode different.
- faf-cli v6.1–6.3 — Go/Rust/Python detection, /faf-go reimagined, desktop notifications via OSC 9.
- claude-faf-mcp v5.5 — Desktop Extension (.mcpb). One-click install. No JSON, no terminal.
- faf-scoring-kernel — Mk4 WASM kernel embedded across the ecosystem. The Foundry compounding.
- The Ghostty-Inspired Edition — Trophy unlocks pop in macOS Notification Center. 10 lines of code.
The Trajectory
What's Compounding
faf-scoring-kernel — six weeks old, 1,723 downloads, last calendar week up 70% on the prior. The Mk4 WASM scorer ships embedded across the CLI, the MCPs, and direct integrators. Every consumer of the kernel is another point of leverage on the .faf compiled-output contract.
The binary is the spec. The score is baked in at compile time. Every install of the kernel widens the floor under everything else.
One Count
Same rule as 50k. We don't pick a registry — we count them all.
FAF ships in TypeScript, Python, and Rust. It runs on npm, PyPI, and crates.io. The downloads are real no matter which registry they come from.
60k+. One count. All platforms. Same number everywhere.
What's Next
IETF engagement live. RadioFAF live with caller-radio chaos. Slash routing every Grok call. The Foundry kernel embedding wider every week.
The format keeps spreading because the format keeps working.