Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@modelstatus/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@modelstatus/cli
Track which AI models you use, where, and never get surprised by a retirement.
The free CLI + TUI for LLM Status — scans your repo for AI model usage (OpenAI, Anthropic, Google, Mistral, DeepSeek, xAI, Moonshot, Cohere, and dozens more) and joins it to a constantly-updated lifecycle registry so you find out before gpt-4 retires, not after.
npx @modelstatus/cli statusThat's it. No sign-in, no account, no telemetry — just a snapshot of every model in your repo plus health badges and replacement suggestions.
Install
Pick whichever fits your stack:
# Self-contained binary, no Node required:
curl -fsSL https://llmstatus.ai/install.sh | bash
# Via npm (needs Node ≥18):
npm i -g @modelstatus/cliOr skip install entirely and one-shot it: npx @modelstatus/cli status.
Quick start
Free: offline health check
mm status [dir] # if installed
npx @modelstatus/cli status [dir] # zero install (needs Node)Pulls the signed registry snapshot from cdn.llmstatus.ai (Ed25519-signed, anti-rollback, ~225 kB), scans the directory, resolves every model id, and prints what you use along with its health:
LLM Status — registry 20260528T013239Z (today), 380 models
Scanned ./apps/web: 12 reference(s) → 6 model(s), 1 custom
Models in use:
🔴 retired openai/gpt-4-0314 retires 2024-06-13 → openai/gpt-4-1 (2)
🟠 retiring anthropic/claude-opus-4 retires 2026-06-15 → anthropic/claude-opus-4-7 (1)
🟢 ok openai/gpt-5 (3)
⚠ 2 model(s) need attention before they retire.Works fully offline after the first run (cached snapshot at ~/.config/llmstatus/registry-cache.json).
Sign in for cloud features
mm login # browser sign-in, polls for completion
mm scan # scans + uploads to your account's inventory
mm # launches the TUI: inventory, scan, what's-new, alerts
mm upgrade # Stripe checkout for Pro (alerting)You get two binaries — mm (short) and llmstatus (descriptive). Same binary, take your pick.
Commands
| Command | What it does |
|---|---|
mm status [dir] |
Free offline model-health check — no account |
mm |
Launch the TUI (inventory, scan, what's-new, alerts, account) |
mm login [api_key] |
Browser sign-in with polling (or paste a key) |
mm signup |
Create an account in the browser |
mm scan [dir] |
Scan for model usage; interactive TUI, or --ci/--json for pipelines |
mm sources |
List detection sources and whether each can run here |
mm upgrade |
Open Stripe checkout, poll until Pro is active |
mm logout |
Forget the saved API key |
Scan sources (--sources, default filesystem; all for everything):
| Source | Reads from |
|---|---|
filesystem |
repo files |
env |
live process env vars (OPENAI_API_KEY, …) |
aws-secrets |
AWS Secrets Manager + SSM |
k8s |
kubectl secrets + configmaps |
helm |
helm release values |
sql |
psql, via --db <dsn> |
Secret sources shell out to your already-authenticated CLIs, run read-only, REDACT every snippet, and only ever upload model ids — secret values never leave your machine. Use --dry-run to preview.
Common flags: --api <url> · --key <key> · --project <id|name> · --yes · --json · --ci · --dry-run · --sources <list> · --region <r> · --namespace <ns> · --kube-context <c> · --db <dsn> · --sql-table <t>
Free vs paid
| Free (this CLI) | Pro (signed in) | |
|---|---|---|
mm status on any repo |
✓ unlimited | ✓ |
| Signed registry snapshot, offline cache | ✓ | ✓ |
| Resolve + health locally, on-device | ✓ | ✓ |
Secret-source aware (env, aws-secrets, k8s, helm, sql) |
✓ | ✓ |
| Cloud inventory across projects/teams | — | ✓ |
| Alerts on deprecations/retirements (email/Slack/SMS) | — | ✓ |
| CI integrations + web dashboard | — | ✓ |
How the registry distribution works
The registry is published as a date-versioned, signed snapshot on Cloudflare R2 at cdn.llmstatus.ai, with a mini-TUF trust chain:
pinned root key (in the CLI binary)
→ root-signs ─→ keys.json (names the current signing key)
→ signing-key-signs ─→ latest.json (pointer, with sha256)
→ blob: <version>.json (immutable)The CLI verifies every byte before trusting the snapshot, refuses any rollback to an older version, and falls back to its local cache when the network's down. The signing key can be rotated without shipping a new CLI release.
Links
- Website: llmstatus.ai
- Pricing: llmstatus.ai/pricing
- Contact / bugs: it@llmstatus.ai
License
MIT © LLM Status