One Binary, Every Package Manager: Shipping a Rust CLI To PyPI, Npm, Homebrew, Winget, and Beyond
summary
A Rust CLI named evnx for validating and secret‑scanning .env files is built, cross‑compiled into platform binaries and published to PyPI, npm, Homebrew, Scoop, Winget and Docker via automated CI. The playbook uses Maturin for Python wheels, npm wrappers, cargo‑dist for Homebrew taps, GitHub Actions producing SARIF, pre‑commit hooks and cosign provenance attestations. Result: thousands of installs in weeks, Winget triggers false‑positive Trojan scans until binaries are code‑signed.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:26The .env file problem
- 6:07Why EVNX in Rust
- 7:33Rust with Cargo
- 10:02Challenges distributing CLI
- 11:05Build once ship everywhere
- 13:11Cross-compilation for platforms
- 15:00Supply chain risks
- 16:02Rust binary for PyPI
- 18:28npm for JavaScript
- 21:17Homebrew distribution
- 23:47Winget submission
- 25:55GitHub Actions setup
- 26:37AI coding skills
- 27:20Summary
- 29:27Q&A
related talks
38mHow I Convinced the World's Largest Package Manager to Use Rust, and So Can You!
47mIt's all in the delivery
57mZen and the Art of Package Management
29mBridging the worlds: pixi reimplements pip and conda in Rust
46mZen and the Art of Convincing Your Company to Use Rust
22mShipping a Solid Rust Crate
21mShipping uv's binaries to millions of machines
31mBuilding an extremely fast Python package manager, in Rust