Documentation

Understand the machine around your code

Envidence records the environment Git ignores, captures what changes while a command runs, and turns a failure into a reviewable case. These pages cover installation, daily use, safety, and the limits you should know.

New here?

Start with Getting started. It takes you from a global install to your first recorded failure in a few minutes.

Quick start

Envidence works best when it has a known-good snapshot to compare against. Create one before you start changing the machine, then wrap the command that matters.

Terminal

npm install -g envidence

cd /path/to/project
evd init --label "Known good"
evd watch -- npm test

evd why

Browse the documentation

Getting started

Install, initialize a project, and run your first command.

How it works

Snapshots, command windows, ranking, and evidence.

Dashboard

Review a case in the local browser interface.

Reports

Create and share a self-contained HTML case file.

Rollback

Preview, apply, and undo a remediation plan.

Configuration

Store locations, settings, and retention.

Commands

Every command, flag, and common workflow.

Privacy

What is stored, how secrets are handled, and how to delete evidence.

Security

Local server controls, rollback gates, and report safety.

Limitations

Platform coverage, evidence gaps, and known edges.

What Envidence is not

Envidence is not a backup tool, a package manager, or a replacement for Git. It records the machine state that surrounds a command. It does not read your personal documents, browser history, SSH keys, cloud credentials, or source file contents.

Findings are ranked leads based on the evidence that was collected. A high score does not prove that a change caused the failure. The how it works page explains the difference between correlation and proof.

Project links

Node.js 24 or newer is required. Windows 10 and 11 have the broadest collector coverage. macOS and Linux use a smaller fallback set.