Manifesto

The Problem

Standalone CLI tools (linters, formatters, code generators, utilities,etc.) are self-contained binaries. They have no transitive dependencies, no version conflicts with each other, no diamond dependency problems to solve. Yet we distribute them through the same heavyweight registries designed for libraries with complex dependency graphs. Homebrew, for example, wraps every tool in a formula that passes through a central review process, rebuilds bottles across a matrix of macOS versions, and pulls in a full tap repository, providing an infrastructure built for managing system-level packages with deep dependency trees, not for delivering a single binary that is already compiled and ready to run.

The result is process overhead without a matching benefit. Homebrew formulas need maintainer approval. CocoaPods trunk demands registration. Every tool that flows through a central registry inherits the registry's bottlenecks, politics, and attack surface.

Even tools designed specifically for CLI tool management add unnecessary layers. Mint points directly to Git repositories (no registry), but it clones source and compiles locally requiring Xcode and the Swift toolchain even when the binary is already built and published. mise is a capable polyglot manager, but it bundles version management, task running, environment variables, a plugin system, and its own tool registry; a Swiss-army-knife when all you need is to download a binary. Both are good tools solving broader problems. For the narrow case of installing a pre-built standalone binary, they carry unnecessary complexity.

The Security Reality

Central registries create concentrated attack surfaces. In 2024, CocoaPods Trunk disclosed three critical CVEs: pod takeover via unclaimed namespaces (CVE-2024-38368), remote code execution via email validation (CVE-2024-38366), and session hijacking through email header manipulation (CVE-2024-38367). Any pod author's account could have been silently compromised.

PyPI faced over 500 coordinated typosquatting attacks, distributing malware through packages named one character off from popular libraries. The centralized model makes this possible: one namespace, one search index, one place where a typo becomes an attack vector.

The Pattern Shift

The industry is already moving away from centralized submission processes. Swift Package Manager replaced CocoaPods' centralized trunk with direct Git URLs, avoiding spec submission and approval queue. SPM still solves the harder problem of dependency resolution for libraries, but the key insight is its distribution model: you point to a repository and a version, and no central authority decides what gets published.

AI agent skills are following the same pattern. Anthropic defines a format standard (YAML frontmatter in Markdown), not a submission process. Any developer can publish a skill by hosting it in a Git repository.

"Define a format standard, not a submission process."

Luca's Approach

Luca installs standalone CLI binaries from any URL that serves them, such as GitHub Releases, S3 buckets, or any HTTP endpoint. It operates at the protocol level: give it a URL to a binary archive, and it handles the rest. No formula to write. No registration to complete. No spec to submit. No approval to wait for.

GitHub Releases happen to be a natural fit. They provide versioning through Git tags, CDN delivery, checksums for integrity verification, and multi-platform artifacts in a single release although they are not a requirement. The trade-off is honest: without a central registry, there's no discovery index. You need to know what you want to install. For standalone dev tools, that's usually not a problem as developers choose their linters, formatters, and build tools deliberately, not by browsing a catalog.