A terminal UI (TUI) for exploring, auditing, and cleaning developer cache directories on macOS and Linux. Scan cached packages for known CVEs, find outdated dependencies, and reclaim disk space — all from one tool.

Developer machines accumulate tens of gigabytes of invisible cache data — ML models, package archives, build artifacts, downloaded bottles. ccmd makes it all visible, scannable for vulnerabilities, and safely deletable.

Why

• ML models (HuggingFace, PyTorch, Whisper) — tens of GB you forgot about
• Package caches (pip, uv, npm, Yarn, pnpm, Bun, Cargo, Maven, Gradle, Go, Homebrew) — old versions with known CVEs
• Xcode DerivedData — often 50–200 GB on macOS dev machines; never cleaned
• Swift Package Manager — reclaim space from cached git clones and artifacts; no CVE scanning yet (OSV SwiftURL coverage is sparse)
• npm supply chain risk — transitive deps with install scripts hiding in npx cache
• Build artifacts (pre-commit hooks, Prisma engines) — stale and re-downloadable

ccmd gives you a single view across all of them with security scanning built in.

Install

Homebrew (macOS and Linux, includes MCP)

brew tap juliensimon/tap
brew install ccmd

From crates.io

cargo install ccmd                  # TUI only
cargo install ccmd --features mcp   # TUI + MCP server for AI integration

With cargo-binstall (prebuilt, includes MCP)

From source

git clone https://github.com/juliensimon/cache-commander
cd cache-commander
cargo build --release
./target/release/ccmd

Prebuilt binaries (includes MCP)

Download from GitHub Releases — available for macOS (x86_64, Apple Silicon) and Linux (x86_64, aarch64).

Quick Start

ccmd                            # browse all default cache locations
ccmd --vulncheck                # scan for CVEs on startup
ccmd --versioncheck             # check for outdated packages on startup
ccmd --root ~/.cache/huggingface  # scan a specific directory

Features

Browse and Understand

• Two-pane TUI — navigable tree on the left, details on the right
• 21 cache providers — semantic names instead of hash directories
• Safety levels — green (safe to delete), yellow (may cause rebuilds), red (contains state)
• Sort by size, name, or last modified
• Search with / — case-insensitive filter across the tree

Security Scanning

• Vulnerability scanning — queries OSV.dev for known CVEs in cached packages
• Version checking — compares cached versions against PyPI, crates.io, and npm registries
• Fix versions — shows which version resolves each CVE, with upgrade commands
• npm supply chain — scans transitive deps in npx cache, flags packages with install scripts
• Filter by status — dim non-vulnerable items to focus on what matters
• Copy upgrade command — press c to copy pip install pkg>=version to clipboard

Clean Up

• Mark and delete — Space to mark, d to delete with confirmation
• Bulk mark — m marks all visible (non-dimmed) items after filtering
• Workflow: scan (V) → filter (f) → mark all (m) → delete (d)

Platform Support

macOS and Linux only. Windows is not supported. Path detection, cache directory resolution, and provider logic all assume Unix-style paths.

Supported Caches

Provider Capabilities

All providers support tree navigation, size display, and deletion. This matrix shows which optional capabilities each provider implements.

Legend:

• Safe = re-downloadable, free to delete (shown with ● in the detail panel).
• Caution = deletion triggers rebuild / re-fetch cost (shown with ◐).
• Unsafe = deletion breaks the tool itself (shown with ○).
• — = not supported for this provider.

Notes:

• ¹ SwiftPM is intentionally disk-hygiene only in v1. Swift package identity in the on-disk repositories/ layout requires parsing git refs, which is too brittle; OSV's SwiftURL ecosystem has sparse coverage; and Swift package upgrades are project-local (Package.swift / Package.resolved), not global cache operations. May be reconsidered when OSV coverage improves.
• ² Xcode has no package-manager ecosystem — its caches are build artifacts, not packages. Vulnerability scanning, version checking, and upgrade commands don't apply.

Key Bindings

Navigation

Security

Marking and Deleting

Other

Configuration

Create ~/.config/ccmd/config.toml:

roots = ["~/.cache", "~/Library/Caches", "~/.npm", "~/.cargo/registry"]
sort_by = "size"          # size | name | modified
sort_desc = true
confirm_delete = true

[vulncheck]
enabled = false           # set true to scan on startup

[versioncheck]
enabled = false           # set true to check on startup

CLI flags override config file values.

How It Works

Cache Detection

ccmd walks your cache directories and identifies providers by directory name and structure. Each provider has custom logic to decode semantic names — for example, HuggingFace stores models in directories like models--meta-llama--Llama-3.1-8B, which ccmd displays as [model] meta-llama/Llama-3.1-8B.

Vulnerability Scanning

When you press V (or pass --vulncheck):

1. ccmd walks the cache tree to discover packages with identifiable name + version
2. Sends a batch query to the OSV.dev API (chunked to 100 packages per request)
3. For each vulnerability found, fetches the detailed advisory to extract fix versions
4. Filters out vulnerabilities already fixed by the installed version
5. Displays results in the detail panel with fix version, upgrade command, and advisory link

npm Supply Chain Detection

The npx cache (~/.npm/_npx/) contains full node_modules trees. ccmd scans every transitive dependency for:

• Known CVEs via OSV.dev
• Install scripts (preinstall, install, postinstall) — the primary vector for supply chain attacks
• Dependency depth — whether a package is a direct dependency or deep transitive

Filter and Clean Workflow

The intended workflow for cleaning vulnerable packages:

1. Scan: Press V to scan all packages for CVEs
2. Filter: Press f to show only vulnerable items (non-matching items are dimmed)
3. Review: Navigate to see fix versions and upgrade commands
4. Mark: Press m to mark all vulnerable items for deletion
5. Delete: Press d to delete — frees space and forces fresh downloads

MCP Server (AI Integration)

ccmd includes an MCP server that lets AI assistants like Claude query and manage your caches conversationally. Build with the mcp feature and run ccmd mcp to start the stdio transport.

# Install with MCP support
cargo install ccmd --features mcp

# Or build from source
cargo build --release --features mcp

Configure in Claude Code:

claude mcp add ccmd -s user -- ccmd mcp

Then ask Claude things like:

"list my caches"

┌──────────────────┬────────────┬───────┐
│     Provider     │    Size    │ Items │
├──────────────────┼────────────┼───────┤
│ HuggingFace Hub  │ 28.93 GiB  │ 447   │
│ ~/Library/Caches │ 11.18 GiB  │ 234   │
│ uv               │ 3.16 GiB   │ 149   │
│ Homebrew         │ 1.55 GiB   │ 170   │
│ Cargo            │ 719.77 MiB │ 614   │
│ ...              │            │       │
└──────────────────┴────────────┴───────┘
Total: ~53.6 GiB across 2,167 items

"find the most vulnerable npm packages"

"find outdated packages in my cache"

Available tools: list_caches, get_summary, search_packages, get_package_details, scan_vulnerabilities, check_outdated, preview_delete, delete_packages. See docs/mcp.md for full details.

Architecture

src/
├── main.rs              # CLI bootstrap, terminal setup, subcommand routing
├── config.rs            # TOML config + CLI flag merging
├── app.rs               # Event loop, key handling, rendering
├── tree/
│   ├── node.rs          # TreeNode, CacheKind enum
│   └── state.rs         # TreeState, FilterMode, visibility, marking
├── scanner/
│   ├── mod.rs           # Background scan orchestrator, package discovery
│   └── walker.rs        # Directory traversal, size calculation
├── providers/
│   ├── mod.rs           # Provider dispatch, safety levels, upgrade commands
│   ├── huggingface.rs   # HuggingFace Hub semantic decoding
│   ├── pip.rs, uv.rs    # Python package providers
│   ├── npm.rs           # npm + npx + node_modules scanning
│   ├── cargo.rs         # Rust crate provider
│   └── ...              # 15 more providers (Yarn, pnpm, Bun, Maven, Gradle, Go, SwiftPM, Xcode, Homebrew, …)
├── security/
│   ├── mod.rs           # Scan orchestration, vulnerability filtering
│   ├── osv.rs           # OSV.dev API, version comparison, fix extraction
│   └── registry.rs      # PyPI, crates.io, npm, Maven Central, proxy.golang.org lookups
├── mcp/                 # MCP server (optional, behind `mcp` feature flag)
│   ├── mod.rs           # ServerHandler, tool routing, cache scanning
│   ├── tools.rs         # Tool parameter and response types
│   └── safety.rs        # Delete safety enforcement
└── ui/
    ├── tree_panel.rs    # Left pane — tree with status icons
    ├── detail_panel.rs  # Right pane — metadata, vulns, guidance
    ├── dialogs.rs       # Delete confirmation, help overlay
    └── theme.rs         # Color and style constants

• No async runtime for TUI — pure std::thread + mpsc::channel
• MCP server uses tokio — optional feature flag, only compiled when needed
• Flat arena tree — avoids recursive structs and borrow checker issues
• Background scanning — UI stays responsive during API calls and directory walks

Contributing

Contributions and feedback are welcome!

• Bug reports & feature requests — open an issue
• Pull requests — fork the repo, create a branch, and submit a PR. Please run cargo fmt and cargo clippy before submitting.
• New cache providers — adding support for a new tool? Start with docs/adding-a-provider.md — it covers the wire-up sites, the OSV/registry design questions, and the test-sharpening rules distilled from every provider we've shipped so far.
• Questions & ideas — feel free to start a discussion or reach out directly.

Author

Julien Simon — julien@julien.org — github.com/juliensimon

License

MIT — see LICENSE for details.