Install the OCM CLI
The OCM CLI is the primary tool for creating, managing, and transferring component versions. This guide covers installation options for different platforms.
You’ll end up with
- The OCM CLI installed and ready to use on your system
- The ability to run
ocmcommands from your terminal
Estimated time
~5 minutes
Install the OCM CLI
The binary is installed to ~/.local/bin by default (per the
XDG Base Directory Specification).
The installer verifies binary integrity via
GitHub attestations when the
GitHub CLI (gh) is available.
Run bash -s -- --help after the pipe to see all options.
Windows Support
The install script only supports macOS and Linux. Windows binaries can be downloaded directly from the GitHub releases page.
Windows support is best-effort and not guaranteed. While the CLI handles Windows-specific
conventions such as drive-letter paths (e.g., C:\path\to\archive) and backslash path separators,
there is no dedicated Windows CI infrastructure to continuously validate these code paths.
- Windows builds are cross-compiled and checked for compilation correctness.
- Windows-specific logic (such as path detection and normalization) is tested via simulated OS behavior on non-Windows runners.
- There is no runtime testing on actual Windows environments in CI.
- Bugs specific to Windows runtime behavior may go undetected until reported.
If you encounter a Windows-specific issue, please report it at github.com/open-component-model/open-component-model/issues.
Verify Installation
After installing, verify the CLI is working:
ocm versionExpected output:
{"major":"0","minor":"1","patch":"0","gitVersion":"0.1.0","goVersion":"go1.26.0","compiler":"gc","platform":"darwin/arm64"}CLI Reference
For detailed command documentation, see the OCM CLI Reference.
Next Steps
- Tutorial: Create component versions - Learn how to create and store component versions using the OCM CLI