Install ohi

Install the ohi command-line tool to search and download ontologies from your terminal. The same tool also runs the LinkML commands, under ohi linkml. For Python or TypeScript applications, see SDK installation.

Install

Supports Intel and Apple silicon Macs running macOS 14 or later, Linux on x86_64 or arm64, and Windows on x86_64.

Bash / Zsh
PowerShell

Run this in Zsh on macOS, Bash on Linux, or Git Bash, MSYS2, Cygwin or WSL on Windows:

. <(curl -sSfL https://ohi.dev/install.sh)

The installer downloads the latest release, verifies its checksum and puts ohi in ~/.local/bin. Accept its offer to add that directory to your shell profile so ohi works in new terminals too.

Run the same command again to update.

Run this in Windows PowerShell 5.1 or PowerShell 7:

irm https://ohi.dev/install.ps1 | iex

The installer downloads the latest release, verifies its checksum and puts ohi.exe in $HOME\.local\bin. Accept its offer to add that directory to your PowerShell profile so ohi works in new terminals too.

Run the same command again to update.

Check the installation

ohi version

You should see the installed version. Then download your first ontology.

Installer settings

Both installers take the same environment variables:

Variable	Effect
`LINKML_SCALA_VERSION`	Install this release tag instead of the latest one.
`LINKML_SCALA_INSTALL_DIR`	Install into this directory instead of `~/.local/bin`.
`LINKML_SCALA_REQUIRE_CHECKSUM=1`	Refuse releases that publish no checksum file. Releases up to and including v0.12.0 have none.

Other ways to install

mise

If you use the mise tool manager, on any platform:

mise use 'ubi:NeverBlink-OSS/ohi[matching=ohi,exe=ohi]'

Manual download

Download the ohi binary for your system and architecture from the latest release.

On macOS and Linux, rename it, make it executable and run it:

mv ohi-<os>-<arch> ohi
chmod +x ohi
./ohi version

On Windows, rename it and run it:

ren ohi-windows-x86_64.exe ohi.exe
.\ohi.exe version

Java

On other systems, download ohi.jar from the same release and run it with Java 17 or later:

java -jar ohi.jar version

Verify a download

Each release publishes a SHA256SUMS file and a signed build provenance attestation, so you can check that a download came from our release workflow. The installers check the checksum for you. To check a manual download, see Verifying downloads.