wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About
  • What is WinGet?

© 2026 winget.ragerworks.com

Loading...
Install Ledgerful using WinGet - wingetCollections
  1. Go back
  2. Packages
  3. Ledgerful
Ledgerful logo

Ledgerful Ledgerful, LLC

change-intelligence cli developer-tools local-first provenance verification
Use this command to install Ledgerful with WinGet:
winget install --id=Ledgerful.Ledgerful -e

Ledgerful: A Local-First Command-Line Tool for Change Intelligence

Ledgerful is a local-first command-line tool designed to provide deterministic change intelligence within your development workflow. It offers essential capabilities such as impact and risk analysis, signed provenance for code changes, verification planning, and local knowledge-graph indexing. This powerful tool ensures developers can make informed decisions by understanding the implications of their code modifications.

Key Features:

  • Impact Analysis: Automatically assesses the potential effects of code changes on your project, helping you anticipate risks and consequences.
  • Provenance Tracking: Ensures every change is recorded with signed provenance, providing a transparent history of modifications.
  • Verification Planning: Generates deterministic verification plans to guide testing efforts, enhancing code quality and reliability.
  • Local Knowledge-Graph Indexing: Builds a comprehensive index of your codebase for efficient querying and analysis without relying on external services.

Target Audience and Benefits:

Ideal for developers and DevOps teams seeking deterministic insights into their code changes, Ledgerful offers:

  • Enhanced decision-making through clear impact assessments.
  • Improved code quality with structured verification plans.
  • Transparent change tracking, fostering trust among team members.

Install Ledgerful via winget to integrate it seamlessly into your workflow. This tool empowers you to manage code changes effectively and maintain high standards of software development.

README

Ledgerful

Ledgerful is a local-first Rust CLI for change intelligence and Gemini-assisted development. It turns repository edits into deterministic impact packets, risk summaries, hotspot rankings, targeted verification plans, and bounded Gemini context.

The tool is designed to stay local and explain its work. It does not act as an autonomous coding agent.

Ledgerful: existing ledgerful commands, hooks, and .ledgerful/ state directories keep working unchanged. New installs also provide ledgerful and the short ldg alias.

Install

Windows (PowerShell):

iwr https://raw.githubusercontent.com/Ryan-AI-Studios/Ledgerful/main/install/install.ps1 -UseB | iex

macOS and Linux:

curl -fsSL https://raw.githubusercontent.com/Ryan-AI-Studios/Ledgerful/main/install/install.sh | sh

cargo-binstall (prebuilt GitHub release binary; no crates.io, no full compile when assets match):

cargo binstall --git https://github.com/Ryan-AI-Studios/Ledgerful

Package managers:

  • Homebrew: brew install Ryan-AI-Studios/tap/ledgerful
  • Scoop: scoop bucket add ledgerful https://github.com/Ryan-AI-Studios/scoop-bucket then scoop install ledgerful
  • winget: winget install Ledgerful.Ledgerful (accepted 2026-07-30; community package version may lag engine releases)
  • Apt and other distro packages are not planned. Manifests and release-time bump automation live under packaging/; channel details in docs/package-distribution.md.

If ledgerful --version is older than the latest published release, you may have multiple installs on PATH — see the PATH / version FAQ.

Manual install from a checkout (compiles from source):

cargo install --path .

The LSP daemon is behind an optional feature:

Versions
0.2.7
0.2.6
0.2.5
0.2.4
0.1.9
Website
github.com
License
Last updated
8/9/2026
Download latest version
Loading...
cargo install --path . --features daemon

See docs/installation.md for installer options, release assets, package managers, and agent bootstrap instructions.

Quickstart

ledgerful init
ledgerful doctor
ledgerful index
ledgerful scan
ledgerful impact
ledgerful verify
ledgerful hotspots
ledgerful ask "What should I verify next?"

Commands

  • init: create .ledgerful/, starter config, starter rules, and .gitignore wiring.
  • doctor: report platform, shell, path, and tool health.
  • index: parse source code to build structural, entrypoint, call-graph, data-model, observability, and semantic vector indices. Supports SCIP ingestion.
  • scan: summarize staged and unstaged git changes.
  • watch: debounce file-system events into persisted batches.
  • impact: generate latest-impact.json with symbols, imports, runtime usage, complexity, temporal coupling, hotspots, CI predictions, and federated impact.
  • verify: build and run a deterministic verification plan using structural impact, temporal coupling, CI predictions, and Bayesian failure probability ordering. Includes --explain for LLM failure rationales.
  • ask: send sanitized impact context to Gemini or a local LLM. Supports natural-language --semantic codebase search.
  • search: sub-millisecond regex search via Tantivy trigrams and ranked BM25 codebase queries.
  • hotspots: rank files by temporal change frequency multiplied by complexity.
  • surfaces (alias tour): read-only inventory of advanced surfaces (ready / empty / gated). Does not enable coverage. Engine dogfood uses committed .env.example + policies/ so schema and security can show ready after index.
  • mcp: run the Model Context Protocol stdio server for AI agent integration; also mcp install|uninstall|status for Top-N host config (claude-code, cursor, codex, copilot).
  • viz: export an interactive HTML Knowledge Graph visualization of codebase dependencies and risk heatmaps.
  • federate: export public interfaces, scan sibling repositories, and show live federated peers (path identity; federate scan prunes stale cache).
  • ledger: transactional architectural memory (start, commit, rollback, audit, search, adr).
  • daemon: optional LSP server with diagnostics, Hover, CodeLens, stale-data handling, and lifecycle management.
  • reset: remove derived local state. Preserves ledger.db by default; use --include-ledger to remove provenance data.
  • demo: generate a synthetic invoice-service repo with real signed ledger entries and a SOC2 evidence export. Fully offline, ~15-30s; cleans up by default (--keep to inspect).
  • export evidence: export a SOC2 evidence zip from the CLI (same artifact as the dashboard button). --profile soc2 --out [--force].
  • timings: local-only command self-timing (which of your commands is slow, and why). See docs/self-timing.md.

Common Workflows

Generate an impact report using first-parent git history:

ledgerful impact

Include all parent traversal for merge-heavy repositories:

ledgerful impact --all-parents

Run predictive verification:

ledgerful verify

Disable prediction and use rule-only verification:

ledgerful verify --no-predict

Inspect risk hotspots:

ledgerful hotspots --limit 20 --commits 500 --dir src --lang rs
ledgerful hotspots --json

Use Gemini narrative reporting:

ledgerful ask --narrative

MCP agent install (Top-N platforms)

Wire Ledgerful into supported agent hosts with one command (merge-only; never clobbers foreign MCP servers):

# Detect hosts, or pick one: claude-code | cursor | codex | copilot
ledgerful mcp install
ledgerful mcp install --platform cursor --dry-run --json
ledgerful mcp status --json
ledgerful mcp uninstall --platform cursor
Platform idDefault scopeConfig key / notes
claude-codeusertop-level mcpServers in ~/.claude.json (not projects[cwd])
cursorusermcpServers in ~/.cursor/mcp.json
codexuser[mcp_servers.ledgerful] in ~/.codex/config.toml
copilotprojecttop-level servers + "type":"stdio" in .vscode/mcp.json

Launcher: --launcher auto (default) prefers a PATH ledgerful binary with args ["mcp"]; falls back to npx -y @ledgerful/mcp-server (Windows prefers npx.cmd) with a pin-lag warning when the binary is missing. Prefer PATH over npx when both exist — published npm may lag the engine.

Written ≠ connected: a successful install updates config files only. Hosts may still require trust/approve prompts (Codex project trust, Claude Code approve, VS Code MCP trust). Reload the host after install.

Bare ledgerful mcp / ledgerful mcp serve still start the stdio server.

Manual / npm wrapper (optional):

npx @ledgerful/mcp-server

The npm wrapper downloads a checksummed GitHub release binary and launches ledgerful mcp. Set LEDGERFUL_MCP_BIN_OVERRIDE to a local binary for development or CI smoke tests.

Use federated intelligence across sibling repositories:

ledgerful federate export
ledgerful federate scan
ledgerful federate status
ledgerful impact

federate status lists live peers (one row per path; name = folder basename). Run federate scan to refresh discovery and prune dead/self cache rows.

Track changes with transactional provenance:

# Start a transaction before editing
ledgerful ledger start src/main.rs --category FEATURE --message "Add auth module"

# After editing and verifying
ledgerful ledger commit --tx-id  --summary "Added auth" --reason "API needs authentication"

# Quick single-file change
ledgerful ledger atomic src/config.rs --category REFACTOR --summary "Extract config validation" --reason "SRP"

# Lightweight note for docs changes
ledgerful ledger note docs/api.md "Update endpoint docs"

# Check status and reconcile drift
ledgerful ledger status
ledgerful ledger reconcile --all --reason "Intentional local changes"

# Search and audit
ledgerful ledger search "auth logic" --category FEATURE --days 30
ledgerful ledger audit --include-unaudited
ledgerful ledger adr --output-dir docs/adr

cargo run --features daemon -- daemon

Configuration

Ledgerful stores repo-local state in .ledgerful/.

  • .ledgerful/config.toml: runtime configuration, watch debounce, Gemini timeout/context, temporal traversal, hotspot defaults, and ledger settings (enforcement, auto-reconcile, verification gating).
  • .ledgerful/rules.toml: policy rules, protected paths, and required verification commands.

Examples live in docs/examples/config.toml, docs/examples/rules.toml, and docs/examples/LEDGERFUL.md.

Reports And State

Generated state is rebuildable and stays inside .ledgerful/.

  • .ledgerful/reports/latest-scan.json
  • .ledgerful/reports/latest-impact.json
  • .ledgerful/reports/latest-verify.json
  • .ledgerful/reports/fallback-impact.json
  • .ledgerful/state/ledger.db
  • .ledgerful/state/schema.json
  • .ledgerful/state/current-batch.json

Impact packets are redacted before SQLite persistence. Gemini prompts are sanitized and truncated before subprocess execution.

Gemini

Ledgerful shells out to the gemini CLI. Ensure it is on PATH before using ledgerful ask.

  • GEMINI_API_KEY can be supplied from the process environment or a repo-local .env file. .env is ignored by git; use .env.example as the template.
  • By default, routine analyze, suggest, and narrative requests use gemini-3.1-flash-lite for lower latency and cost.
  • High-risk packets and review-patch requests use gemini-3.1-pro for deeper reasoning and code review.
  • Set gemini.model in .ledgerful/config.toml only when you want one explicit model for every ask mode.
  • --mode analyze: blast-radius and risk reasoning
  • --mode suggest: targeted verification recommendations
  • --mode review-patch: patch review with live diff context
  • --narrative: senior-architect risk narrative generated from one structured prompt

If Gemini fails after an impact packet is available, Ledgerful writes a fallback impact artifact or reports why it could not.

Windows / WSL

  • Windows 11 + PowerShell is the primary environment.
  • Mixed Windows/WSL filesystem setups can be slower and may produce different tool availability.
  • Keep git and gemini installed in the environment where you run Ledgerful.

Architecture

See docs/architecture.md for module boundaries and current data flow.

Contributing

  • Questions and setup help: GitHub Discussions.
  • Bug reports: GitHub Issues.
  • Security reports: see SECURITY.md — do not file public issues for security vulnerabilities.
  • Keep changes phase-bounded and deterministic.
  • Run cargo fmt --check, cargo clippy --all-targets --all-features -- -D warnings, and cargo test --all-features -j 1 -- --test-threads=1 before pushing.

License

Ledgerful is source-available under the PolyForm Noncommercial License 1.0.0, with additional permissions for qualified small entities in COMMERCIAL-EXCEPTION.md.

Required Notice: Copyright 2026 Ledgerful, LLC; additional permissions are stated in COMMERCIAL-EXCEPTION.md.