cargo-lbin

cargo-lbin is a Cargo-powered application manager for command-line binaries published on crates.io.

It leaves fetching, dependency resolution and compilation to cargo install, then adds the small lifecycle layer around the resulting applications: discovery, inspection, installation, ownership tracking, update checks, updates and removal.

search -> info -> install -> list -> check updates -> update -> remove

By default, managed binaries live in /usr/local/bin, separate from distribution packages in /usr/bin.

The normal interface is a Cargo subcommand:

cargo lbin ...

Direct invocation as cargo-lbin ... works too.

Why?

Sometimes a Rust CLI is useful enough to install system-wide, but not useful enough to justify writing and maintaining a distro package for it.

cargo install already does the hard part. cargo-lbin deliberately does not replace Cargo's resolver or build process; it manages the installed application afterwards.

/usr/bin        -> distro packages
/usr/local/bin  -> cargo-lbin

It is not a replacement for pacman, rpm, apt, Cargo, or a proper distro package when one is warranted.

Installation

From crates.io:

cargo install cargo-lbin

From a checkout:

cargo install --path .

The terminal UI is enabled by the default tui feature. To build only the CLI, without Ratatui/Crossterm dependencies:

cargo install cargo-lbin --no-default-features

Do not run cargo-lbin itself with sudo. Build scripts and proc macros must run as your normal user; cargo-lbin requests sudo itself only when placement under the canonical /usr/local prefix requires it.

Quick start

# Find a crate when you do not know its exact name
cargo lbin search beerland

# Inspect a crate by exact name
cargo lbin info scx_beerland

# Install it
cargo lbin install scx_beerland

# See everything cargo-lbin manages
cargo lbin list

# Check crates.io for updates
cargo lbin checkupdate

# Update one crate, or all managed crates
cargo lbin update scx_beerland
cargo lbin update --all

# Remove it again
cargo lbin remove scx_beerland

# Or drive the same operations interactively
cargo lbin tui

Commands

Command	Purpose
install <crate[@version]>... [--locked]	Build crates with Cargo and install their binaries; @version installs exactly that version and pins it
remove <crate>...	Remove managed crates and their binaries
pin <crate>... / unpin <crate>...	Hold crates at their installed version / release the hold
downgrade <crate>	Pick an older version from crates.io, install it and pin it
list [--json]	List managed crates, using the last update report for annotations
checkupdate [--json]	Query crates.io for updates and save a full local report
update <crate>... [--yes]	Update explicitly selected managed crates; --yes skips confirmation
update --all [--yes]	Update every managed crate with an available update; --yes skips confirmation
search <terms>... [--limit N]	Find crates by keyword
info <crate>...	Show exact-name crate information and installed state
tui	Interactive frontend over the same operations, when the tui feature is enabled
completions <shell>	Print a shell completion script for the commands and flags

Install

Install one or more crates:

cargo lbin install ripgrep
cargo lbin install ripgrep hexyl

Install exactly one version, and keep it:

cargo lbin install scx_beerland@1.1.2

installed scx_beerland 1.1.2 -> /usr/local/bin (scx_beerland) [pinned; `cargo lbin unpin scx_beerland` to allow updates]

A version chosen by name is a version meant to stay, so @version pins the crate (see Pin); without the pin, the next update --all would rebuild the newest release and leave no trace of the choice. The version must be an exact semver version — foo@^1 is refused, since "any matching version" is what plain install foo already means. Cargo refuses yanked versions; info shows which ones those are. Installing a named version over an already pinned crate is allowed — it is a re-pin to that version — whereas a bare install foo on a pinned crate is refused, because it would build the newest release. A crate may appear only once per install command, with or without a version: install foo@1.2.3 foo would otherwise end with the newest release pinned, and two builds of one crate in one command is never what was meant.

Build using the crate's committed Cargo.lock:

cargo lbin install some-tool --locked

The --locked choice is stored per crate and reused on future updates.

Installing an already managed crate is a full reinstall: it is rebuilt in a fresh staging directory and its managed binaries are replaced. Changing --locked on a reinstall therefore takes effect instead of being skipped as "already installed".

Installing a binary name the prefix did not have before — every name on a first install, only the added ones when an update introduces a new binary — warns when a file of that name already exists on PATH outside the prefix, usually a distribution package:

warning: `rg` already exists as /usr/bin/rg (/usr/bin/rg is owned by ripgrep 14.1.1-1); /usr/local/bin precedes /usr/bin in PATH

The owner comes from /usr/bin/pacman -Qo, /usr/bin/rpm -qf or /usr/bin/dpkg -S — the first of these that runs and claims the file; by absolute path, never a PATH lookup, since the prefix itself is usually on PATH ahead of /usr/bin. Without a claim, the file is still reported. The warning reports which directory comes first in PATH — the prefix's bin, the existing file's directory, or that <prefix>/bin is not on PATH at all; it does not attempt to determine which file the current user can actually execute. Paths and package-manager output are external data and pass through the same control-character sanitizing as crates.io responses before reaching the terminal. It is a warning, not a refusal: installing a newer version than the distribution ships is a normal reason to use this tool, and the person installing decides.

Search

Find crates by keyword:

cargo lbin search sched_ext scheduler
cargo lbin search beerland --limit 5

Search terms are joined with spaces. --limit accepts 1..=100 and defaults to 10. cargo-lbin honours crates.io's one-request-per-second policy, so back-to-back searches wait for the remainder of the second when necessary.

Example:

* scx_beerland  1.1.3  Scheduler designed to prioritize locality and scalability.  [installed 1.1.2]
  scx_lavd      1.1.3  A Latency-criticality Aware Virtual Deadline scheduler ...
* installed under /usr/local

search uses crates.io's keyword search and preserves its relevance order. Unlike cargo search, it can also mark hits already managed under the selected prefix and show their installed version.

The displayed version prefers the newest stable version reported by crates.io. If none is available, cargo-lbin falls back to crates.io's default version and then its legacy newest-version field. No matches is a valid answer, not an error.

Search results are only a discovery view. Use info when you want the exact release history and update eligibility for a chosen crate.

Info

Show one or more crates by exact name:

cargo lbin info ripgrep bat

Example:

ripgrep
  latest:      14.1.1
  releases:    42 (2 yanked)
  installed:   14.1.0 (update available: 14.1.1)

bat
  latest:      0.26.0
  pre-release: 0.27.0-beta.1
  releases:    38
  installed:   no

latest and pre-release describe published history. They may name a yanked release, which is shown explicitly as [yanked]. The pre-release line is shown only when that release is newer than the latest stable release.

The installed verdict is a separate question. It uses the same non-yanked update rules as checkupdate, so info does not call something "up to date" when checkupdate would disagree. If a crate has no non-yanked releases left, that is reported explicitly.

Unknown names do not stop the rest of a batch. They are reported after the successful results, with a hint to use search; the command exits non-zero if any exact lookup failed.

List and update reports

List managed applications:

cargo lbin list

Example:

hexyl 0.14.0 [pinned] (hexyl) -> 0.16.0
ripgrep 14.1.1 (rg) (up to date)
some-tool 1.2.3 [locked] (some-tool, some-toolctl)
update check: 3h ago

list never touches the network. Update annotations come only from the most recent checkupdate report:

• -> VERSION means a newer version was known at the last check.
• (up to date) means that exact installed version was checked and found current.
• No annotation means the crate was not covered by that report, for example because it was installed or updated afterwards.

The report age is printed to stderr so stdout remains suitable for simple parsing. Without a saved report, list still lists the manifest and tells you that no update check has been recorded.

Run a fresh check with:

cargo lbin checkupdate

Example:

hexyl 0.14.0 -> 0.16.0
some-tool 1.2.3 -> 1.3.0

checkupdate is read-only with respect to installed applications and uses script-friendly exit codes following the pacman-contrib checkupdates convention:

Exit code	Meaning
0	updates are available
1	an error occurred
2	everything is up to date

A successful check writes a full per-prefix snapshot, not merely the outdated entries. Failure to write that presentation cache is a warning; it does not change the result of an otherwise successful update check.

JSON output

list --json and checkupdate --json print one JSON document on stdout and nothing else; warnings stay on stderr and exit codes are unchanged. The shape is a contract: every document carries a schema number, fields are only ever added within a schema version, and any rename, retype or removal is a schema bump.

{
  "schema": 1,
  "prefix": "/usr/local",
  "checked_at": 1756761600,
  "crates": [
    {
      "name": "hexyl",
      "version": "0.14.0",
      "bins": ["hexyl"],
      "locked": false,
      "pinned": true,
      "status": "outdated",
      "latest": "0.16.0"
    },
    {
      "name": "some-tool",
      "version": "1.3.0",
      "bins": ["some-tool", "some-toolctl"],
      "locked": true,
      "pinned": false,
      "status": "unknown",
      "latest": null
    }
  ]
}

list --json fields: prefix is the absolute, normalized prefix; checked_at is the Unix time of the last recorded check, or null if there is none; pinned mirrors the pin state; status is one of up_to_date, outdated or unknown (not covered by the last check — installed or updated since); latest is the newest version that check found, or null when the status is unknown. An empty prefix is "crates": [], not a message.

checkupdate --json prints the snapshot the check just took, with the same schema, prefix and checked_at, and per crate name, current, latest and a derived outdated boolean:

cargo lbin checkupdate --json | jq -r '.crates[] | select(.outdated) | .name'

Update

Update selected crates, or explicitly request all managed crates:

cargo lbin update hexyl some-tool
cargo lbin update --all

A bare cargo lbin update is intentionally a usage error. Once individual updates exist, cargo-lbin never guesses that "update" means "replace everything".

The update plan is printed and confirmed before anything is built. Skip the confirmation prompt with:

cargo lbin update --all --yes
cargo lbin update --all -y

The same flag works with an explicit crate list.

Each selected crate is an independent unit. A failure is reported and the remaining crates are still processed; successful updates are not undone because a later crate failed. The command exits non-zero whenever fewer updates were applied than were confirmed, including a failed build/placement or a crate skipped because the manifest changed between confirmation and execution.

The last update report is never authoritative for mutation. update performs its own fresh checks, and after confirmation it reloads the manifest under the exclusive lock before changing anything.

Pin

Hold a crate at the version it has:

cargo lbin pin hexyl
cargo lbin unpin hexyl

install NAME@VERSION pins as part of installing (see Install); pin is for a crate already in place.

A pinned crate is left out of update --all — listed as [pinned, skipped] so the hold is visible, never silent, and not queried at all, so a pinned crate whose lookup fails cannot stop the others from updating — and refused by update NAME and by install NAME (a reinstall builds the newest version, which is what the pin forbids) until it is unpinned. checkupdate and list still check and report a newer version when one exists: the pin is a decision about what to do with that fact, not a reason to hide it. list marks pinned crates with [pinned], and a pin set by another process between confirming an update and running it counts as changed state, so that crate is skipped. Removing a pinned crate is allowed; a pin holds a version, not a binary.

Pinning writes the manifest, so it needs the same privilege as installing into the prefix.

Downgrade

Go back to an older version without knowing its number:

cargo lbin downgrade scx_beerland

scx_beerland 1.1.3 is installed; older versions on crates.io:
  1) 1.1.2
  2) 1.1.1
  3) 1.0.9
select a version to install (1-3), or Enter/q to abort: 1
downgrading scx_beerland 1.1.3 -> 1.1.2
...
installed scx_beerland 1.1.2 -> /usr/local/bin (scx_beerland) [pinned; `cargo lbin unpin scx_beerland` to allow updates]

The list is crates.io's, filtered by the same release-relevance policy update uses — published, not yanked, pre-releases only when the installed version is one — applied to versions older than the installed one. If the crate is removed or its installed version changes while the prompt is open, the command stops rather than applying a choice made against stale state. Newest first, at most ten; if there are more, install NAME@VERSION takes any of them. The chosen version is built like any install, with the crate's --locked setting carried over, and pinned for the same reason install NAME@VERSION pins: a downgrade the next update --all would undo is not a downgrade.

The command is interactive on purpose and has no --yes; without a terminal it stops and points at install NAME@VERSION, which is what a script that knows the version needs. Any answer other than a listed number, an empty line or q is an error, and the command can simply be run again.

Remove

Remove one or more managed crates:

cargo lbin remove hexyl
cargo lbin remove foo bar

cargo-lbin removes only binaries recorded as belonging to the selected managed crate.

Shell completion

Completion scripts are generated from the same Clap definition as --help, so there is no separate handwritten command specification to maintain. The script is a snapshot of the CLI as of the version that generated it: regenerate it after upgrading cargo-lbin to pick up CLI changes.

cargo lbin completions bash       > ~/.local/share/bash-completion/completions/cargo-lbin
cargo lbin completions zsh        > ~/.zfunc/_cargo-lbin            # with ~/.zfunc in fpath
cargo lbin completions fish       > ~/.config/fish/completions/cargo-lbin.fish
cargo lbin completions elvish     > ~/.config/elvish/lib/cargo-lbin.elv   # then `use cargo-lbin`
cargo lbin completions powershell > $HOME\cargo-lbin.ps1              # then `. $HOME\cargo-lbin.ps1` in $PROFILE

Each of these writes a file that the shell loads; regenerating after an upgrade overwrites it. (Appending to $PROFILE directly would add a second copy on every regeneration — hence the separate .ps1 that the profile dot-sources.)

Static CLI completions only: subcommands, flags and known values (such as the shell names above). They are generated entirely from the command definition and never inspect the installation prefix, so installed crate names are deliberately not completed. The script completes the cargo-lbin binary; cargo-lbin <Tab> always works, while cargo lbin <Tab> depends on whether your cargo's own completion delegates to external subcommands.

TUI

The TUI is an interactive frontend over the same core operations:

cargo lbin tui

┌ cargo-lbin — /usr/local ──────────────────────────────────┐
│ Packages (3)  Updates (2)                                 │
├───────────────────────────────────────────────────────────┤
│ NAME             VERSION       STATUS                     │
│ > ripgrep        14.1.1        ✓ up to date               │
│   bat            0.26.0        ↑ 0.26.1                   │
│   fd             10.2.0        ↑ 10.3.0                   │
├ Selected ─────────────────────────────────────────────────┤
│ Crate      bat                                            │
│ Installed  0.26.0                                         │
│ Latest     0.26.1                                         │
│ Binaries   bat                                            │
├───────────────────────────────────────────────────────────┤
│ ↑/↓ select · Tab filter · Enter/u update · U update all … │
│ 3 packages · 2 updates · checked 3h ago                   │
└───────────────────────────────────────────────────────────┘

The TUI starts entirely from disk — the manifest and the last checkupdate report. It performs no refresh, network request, update or installation on startup.

Key	Action
↑ / ↓, j / k	Move selection
g / G	First / last row
Tab	Switch between Packages and Updates
Enter, u	Update the selected crate
U	Run a fresh update --all
i	Open the install line (NAME[@VERSION]... [--locked]; @VERSION pins)
x	Remove the selected crate after TUI confirmation
p	Pin or unpin the selected crate
D	Downgrade the selected crate; the version prompt appears in the terminal
r	Run checkupdate and refresh the saved report
s	Search crates.io by keyword
1..9	With search results open, pick a visible hit into the install line
?	Show help
q, Esc	Quit from the package list; Esc also dismisses transient views/input

Search and update checks run without freezing the list. Search hits are displayed in the details panel; installed hits are marked, and pressing a digit opens the normal install input with that crate name, still editable so --locked can be added.

The saved update report is presentation only. U always invokes a real update --all and lets that command compute a fresh plan, even if the TUI currently shows zero cached updates.

Operations that need Cargo output or a sudo password (install, update, remove) temporarily hand the real terminal back to the normal CLI. Cargo diagnostics, the update confirmation and password prompt therefore behave exactly as they do outside the TUI; the interface returns afterwards.

Prefixes and cache

The default prefix is /usr/local:

/usr/local/bin
/usr/local/share/cargo-lbin/manifest.json
/usr/local/share/cargo-lbin/lock

Select a custom prefix with --prefix:

cargo lbin --prefix ~/.local install hexyl
cargo lbin --prefix ~/.local list

Or set it once for every invocation:

export CARGO_LBIN_PREFIX="$HOME/.local"
cargo lbin install hexyl
cargo lbin list

Prefix precedence is:

--prefix > CARGO_LBIN_PREFIX > /usr/local

Custom prefixes must be writable by the invoking user. cargo-lbin only permits privilege escalation for the canonical /usr/local prefix; it will not use sudo to write into an arbitrary custom path.

Build staging and the update-report cache live under:

$XDG_CACHE_HOME/cargo-lbin/

or, when XDG_CACHE_HOME is unset:

~/.cache/cargo-lbin/

Builds use per-process staging directories, so independent operations against different prefixes cannot wipe each other's stages.

The last checkupdate snapshot is stored under checkupdate/, one file per normalized prefix. Relative prefixes are anchored to the current working directory before that cache key is derived, so --prefix local in two different directories refers to two different prefix states. The snapshot is presentation-only state: it has no expiry, only checkupdate refreshes it, and it can be deleted at any time.

Update rules

checkupdate, info and update use crates.io release data with the same eligibility rules:

• Yanked releases are never offered as updates.
• Stable installations are offered stable releases only.
• An installed pre-release may move to a newer pre-release or to a stable release. Once installed on a stable version, only stable releases are offered again.
• Versions are compared with SemVer.
• The version written to the manifest is the version Cargo actually built, read from Cargo's staging metadata rather than assumed from an earlier check.
• If a new release stops shipping one of a crate's previously managed binaries, the obsolete binary is removed during the update.

Network errors are reported rather than silently producing an incomplete update list.

search is intentionally different: it is a discovery view backed by the crates.io search API, not the sparse-index update resolver.

Safety model

cargo-lbin is intentionally conservative because it builds third-party crates and may later perform a small number of filesystem operations with elevated privileges.

It does not sandbox Cargo. Installing a crate means trusting code that Cargo may execute as your user, including build scripts and proc macros. The safety model is about keeping that unprivileged build environment from being accidentally promoted into privileged filesystem access during placement.

Builds never run through sudo

Crates are built first, as the invoking user, in an isolated staging root. Only placement into a protected /usr/local destination may trigger sudo.

Running the whole tool as root is rejected:

sudo cargo lbin install foo
# error: cargo-lbin must not be run as root

For root-only containers or CI environments, the guard can be explicitly overridden:

CARGO_LBIN_ALLOW_ROOT=1 cargo lbin ...

Existing files are not silently overwritten

Before placement, every destination name is checked.

A binary may be replaced only when the manifest already records it as belonging to the same crate. A name owned by another managed crate, or an unmanaged file already present at the destination, causes the operation to fail without clobbering it.

The manifest also enforces that every binary name has exactly one owning crate.

Privileged commands use trusted paths

Operations that may run through sudo invoke trusted system tools by absolute path rather than resolving them through the user's $PATH. A build script therefore cannot place a fake sudo, install, mv or similar executable earlier in the path and have the privileged placement code execute it.

Staged binaries are pinned before privileged placement

A staged binary is opened with symlink following disabled and verified as a regular file owned by the invoking user. Privileged placement copies the already-open file descriptor through /proc/<pid>/fd/..., rather than trusting a stage pathname that could be swapped after validation.

Binaries are installed atomically through a temporary file in the destination directory followed by rename. An interrupted replacement therefore does not leave half of a new executable in place of the old one.

The manifest is validated, sealed and committed atomically

State lives at:

<prefix>/share/cargo-lbin/manifest.json

The manifest is treated as untrusted input whenever it is loaded. Crate names, binary names, versions, duplicate ownership and path safety are validated before state can steer filesystem operations.

When writing state, cargo-lbin serializes the manifest into an anonymous Linux memfd, seals it against further modification, reads the sealed bytes back for verification, and only then hands the descriptor to the placement path. The final manifest is installed through a same-directory temporary file and atomic rename.

In short: cargo-lbin does not knowingly write manifest state that it would refuse to read back later.

crates.io data is treated as untrusted input

External registry metadata is normalized before it reaches the CLI or TUI. Control characters are replaced with spaces and whitespace is normalized at the API boundary, returned crate names are validated with the same rules as names supplied by the user, and search-result limits are enforced locally rather than trusted solely to the server.

Concurrent instances are serialized per prefix

Each prefix has a state lock:

<prefix>/share/cargo-lbin/lock

Mutating operations (install, update, remove) take an exclusive lock. Readers take a shared lock only around the manifest snapshot where possible; network queries and the interactive update prompt do not hold the lock.

update reloads and verifies state after confirmation before mutating it, so changes made by another cargo-lbin while the prompt was open are not acted on blindly.

Partial failures stay recoverable

Crates are committed to the manifest one successful operation at a time. A failure later in a batch does not erase earlier successful work.

For multi-binary installs and updates, newly introduced binary names placed before a manifest commit are removed on a best-effort basis if that operation fails. Existing names remain associated with the previous manifest entry and can be safely replaced on retry.

A hard kill or power loss in the narrow window between placing a new binary name and committing the manifest can still leave an unmanaged orphan. cargo-lbin then refuses to overwrite it and asks you to remove the leftover manually before retrying. A persistent transaction journal is intentionally out of scope.

SELinux

After placement, cargo-lbin runs restorecon on installed binaries when it is available in a trusted system location. This is best-effort; systems without SELinux tooling simply skip the step.

Requirements

cargo-lbin currently targets Linux.

• Rust/Cargo 1.91 or newer to build the tool.
• A working Cargo setup.
• Network access to crates.io for installs, searches, exact info lookups and update checks.
• /proc mounted and available for descriptor-based placement.
• sudo when the canonical /usr/local destination is not writable by the invoking user.
• Standard GNU/Linux userland tools in their conventional trusted locations (sudo, install, rm, mkdir, touch, mv, chmod).

The implementation is developed with conventional Arch Linux and Fedora-style layouts in mind.

Non-goals

Keeping the scope small is deliberate. cargo-lbin does not try to become another Cargo or a distro package manager.

It currently does not provide:

• Git or local-path sources (--git, --path).
• Privileged installation into arbitrary custom prefixes.
• Management of libraries, headers, systemd units, configuration files or other distro integration.
• A dependency resolver of its own — Cargo remains responsible for builds and dependencies.
• Automatic background checks, updates or a daemon. The TUI also never refreshes, searches or updates anything on its own.
• Security advisories. Vulnerabilities live in the dependencies compiled into a binary, and cargo-lbin records only the crates it installed, not their dependency graphs; an "audit" of the installed names alone would report clean binaries it had not looked inside. Doing it properly would mean capturing each build's resolved dependency set, keeping an advisory database and matching version ranges — a second tool grafted onto this one. Use cargo audit in a source tree with an appropriate Cargo.lock; cargo-lbin does not claim to audit the dependencies compiled into its installed binaries, and a crate's published lockfile need not match what a build without --locked resolved.

For a normal per-user ~/.cargo/bin workflow, plain cargo install remains the simpler tool.

License

Licensed under either of:

• Apache License, Version 2.0
• MIT License

at your option.