Installation

ovecc ships as a single self-contained binary. There is no runtime to install, no package manager step, and no service to run: the storage engine is bundled inside the executable, and everything works offline.

Prebuilt binaries

Grab the binary for your platform from the ovecc releases page (fresh Linux and Windows x86_64 builds are published on every release):

Platform	Binary
Linux x86_64	ovecc
Windows x86_64	ovecc.exe

Then put it on your PATH.

Linux

chmod +x ovecc
sudo mv ovecc /usr/local/bin/
ovecc --version

Windows (PowerShell)

# from the folder containing ovecc.exe
Move-Item ovecc.exe "$env:LOCALAPPDATA\Programs\ovecc\ovecc.exe" -Force
# add that folder to your user PATH once:
[Environment]::SetEnvironmentVariable('Path',
  "$env:LOCALAPPDATA\Programs\ovecc;" + [Environment]::GetEnvironmentVariable('Path','User'), 'User')
# open a new terminal, then:
ovecc --version

Verify

$ ovecc --version
ovecc 0.1.0

That's the entire installation. The binary is on the large side (~100 MB) because the analysis database engine is statically bundled — the trade-off is that ovecc index . works on a fresh machine with zero additional setup.

What ovecc will (and won't) touch

• ovecc writes its state into a .ovecc/ directory inside the repository you analyze (and adds it to .gitignore for you via ovecc init).
• ovecc never makes network calls, with one explicit, opt-in exception: ovecc audit --fetch downloads public OSV vulnerability advisories into .ovecc/osv/.
• ovecc never modifies your source files unless you explicitly run ovecc fix --apply.

Next step

Head to the quickstart and index your first repository.