install

Additional install commands

macOS

Homebrewverified · 100%

brew install usage

provider-native install command

overview

Package summary

Tool for working with usage-spec CLIs

Project links

Commands and aliases

usage

history

Project history and usage

usage is both a specification and a CLI for describing command-line interfaces. The official README compares a Usage spec to OpenAPI for CLIs, covering arguments, flags, environment variables, and config files so downstream tools can generate completions, documentation, man pages, parsers, SDKs, and framework scaffolding.

Project history

The project grew out of the modern CLI tooling ecosystem around jdx's tools and the KDL document language. Public GitHub releases show early v0.1.x releases in 2024 and v3.x releases in 2026, while the docs describe an expanding scope from shell completions and man pages toward type-safe SDK generation.

Adoption history

The official CLI docs list installation through mise, Cargo, Homebrew, and Arch Linux. The input metadata also records Homebrew, Nix, and pacman package names, indicating adoption by users who want the same CLI-spec tool available across developer workstations and Linux distributions.

How it is used

A Usage spec is written in KDL and can describe a CLI's name, binary, about text, version, author, license, flags, arguments, subcommands, config files, environment variables, and defaults. The `usage` CLI then consumes that spec to generate shell completions, Markdown, man pages, JSON, and related artifacts.

Why package nerds care

Package nerds care about usage because it treats CLI metadata as a portable build artifact. Instead of each package separately hand-maintaining completions, man pages, and docs, maintainers can ship a spec and generate those outputs consistently.

Timeline

2024: Early v0.1.x GitHub releases published.
2026-06-23: GitHub release v3.5.3 published.

Related projects

The official docs relate Usage to OpenAPI for CLIs, KDL as the spec language, and integrations for CLI frameworks such as clap, Cobra, Click, Typer, yargs, oclif, and Commander.js.

Sources

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

Command	Kind	Exposure	Note
`usage`	executable	indexed executable	Discovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03

manager version4.1.0

manager updated2026-07-30

local dataunknown

upstreamnot available

latest detectednot detected

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:usage
Version	4.1.0
Package manager	Homebrew
Homepage	https://usage.jdx.dev/
Repository	https://github.com/jdx/usage
Last updated	2026-07-30T13:39:00Z
Pulse	updated
Bottle	not recorded
Service	none declared

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/usage.yml

Used sources

Geiger risk classifier
Nucleus package database
curated package history
pkgdb category and tag curation

Install usage with Homebrew