Skip to content

Excise, a surgical terminal storage navigator

Excise

Excise is a terminal storage navigator for understanding and surgically removing exactly the files and folders you choose. It combines an interactive storage map with careful space accounting, bounded resource use, safe handling of unusual file names, and a deliberate review before permanent deletion.

Permanent means permanent

Excise deletes confirmed entries without a trash folder or undo. Start with a disposable directory, keep the default confirmation enabled, and read the Permanent Deletion Contract before acting on real data.

  • 🚀 Start safely

    Install Excise, create a disposable fixture, and learn the review flow before scanning anything important.

    Getting Started

  • âš™ Set your defaults

    Configure scan scope, resource budgets, themes, keymaps, and noninteractive report output.

    Configuration

  • 📊 Understand the result

    Choose human-readable table output or versioned JSON, then interpret exact, uncertain, and partial results correctly.

    Reports & JSON Formats

  • 🛡 Review the safety model

    Learn the deletion, accounting, and threat-model contracts that bound what Excise claims and does.

    Safety Contracts

A Map With Explicit Limits

If you need to… Start here
Inspect disk usage interactively Getting Started
Set persistent scan or interface preferences Configuration
Consume stable output in automation Reports & JSON Formats
Understand concurrent scanning, deletion, and storage Architecture
Audit deletion or accounting guarantees Safety Contracts
What Excise does not promise

Excise does not claim a physical-storage total for copy-on-write files, clones, compression, or filesystem deduplication. It keeps uncertainty explicit, never converts an unknown allocation into a guessed value, and never turns a partial scan into deletion authority. See Space Accounting and the Threat Model.

Learn the System

  • Architecture

    The main loop, session coordinator, persistent scanner, immutable ScanStore, and bounded ownership model.

    Read the architecture

  • Background tasks

    Why scan, refresh, planning, and deletion work have fixed queues and explicit ownership.

    Read the decision

  • Safety contracts

    The identity checks, interruption behavior, unknown-space rules, and evidence needed for safe change.

    Read the contracts

  • Project lineage

    Excise’s relationship to Diskonaut and the preserved historical tags.

    Read the lineage

Contribute and Maintain

  • Development covers the toolchain, local verification, generated artifacts, fuzzing, benchmarks, and the documentation site.
  • Release Process defines the exact-commit candidate and promotion procedure.
  • Project Lineage records attribution and the boundary between Excise and its predecessors.

Project Policies

Published Formats

Source

GitHub repository crates.io package