Installation#

ocom is an end-user application, not a library, so install it as a standalone tool rather than as a project dependency. It ships a single ocom command: run ocom interactive to launch the TUI, or use its other subcommands (ocom version, ocom info, ocom --help) as a CLI.

Stable release#

Install ocom into an isolated environment with your preferred tool installer:

uv tool install ocom
pipx install ocom

Or run it without installing:

uvx ocom

On macOS/Linux, install it from the Homebrew tap:

brew install hasansezertasan/tap/ocom

On Windows, install it from the Scoop bucket:

scoop bucket add hasansezertasan https://github.com/hasansezertasan/scoop-bucket
scoop install hasansezertasan/ocom

Verify release provenance#

Public-repository release distributions include Sigstore-signed build provenance. After downloading a wheel or source distribution, verify that the release workflow built it from main in this repository:

gh attestation verify <downloaded-distribution> \
  --repo hasansezertasan/ocom \
  --signer-workflow hasansezertasan/ocom/.github/workflows/release.yml \
  --source-ref refs/heads/main

Artifact attestations are available for public repositories on current GitHub plans. Private and internal repositories require GitHub Enterprise Cloud and the repository variable ENABLE_PRIVATE_ATTESTATIONS=true.

From source#

The source files for ocom can be downloaded from the GitHub repo.

You can either clone the public repository:

git clone https://github.com/hasansezertasan/ocom.git

Or download the tarball:

mkdir ocom
curl -fL https://github.com/hasansezertasan/ocom/tarball/main | tar -xz --strip-components=1 -C ocom

Once you have a copy of the source, you can install it with:

cd ocom
uv tool install .