# Install oslo with Homebrew

CLI tool for the OpenSLO spec. Version 0.13.0 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:oslo
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install oslo
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:oslo
- **Package manager:** Homebrew
- **Version:** 0.13.0
- **Source summary:** CLI tool for the OpenSLO spec
- **Homepage:** <https://openslo.com/>
- **Repository:** <https://github.com/openslo/oslo>
- **Last updated:** 2026-07-27T23:46:53+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- oslo (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.13.0
## Project history and usage

oslo is the validation and formatting CLI for OpenSLO, an Apache-2.0 specification for declaring service-level objectives as YAML or JSON. It exists to make SLO definitions fit into Git and CI workflows rather than remaining vendor-specific dashboard configuration.

### Project history

The OpenSLO specification repository was created on April 27, 2021, and the oslo CLI repository followed on April 30, 2021. That close pairing reflects the project's shape: a vendor-agnostic SLO document format plus a command-line tool that checks and normalizes those documents.

OpenSLO's public site describes the specification as a service-level objective language for declarative reliability and performance targets, released under Apache 2.0. The specification states goals of Kubernetes-YAML compatibility, vendor neutrality, and extension points for implementation-specific needs.

### Adoption history

The oslo README documents several distribution paths: prebuilt release assets, `go install`, Homebrew through the OpenSLO tap, Docker images from GitHub Container Registry, and source builds. That mix points at CI-oriented usage, where teams can validate SLO manifests during code review or deployment.

### How it is used

The core commands are deliberately narrow: `oslo validate` checks OpenSLO YAML or JSON documents, and `oslo fmt` formats them. OpenSLO's homepage frames this as a GitOps workflow: run the CLI in any CI/CD tool so SLO files are well-formed before they are consumed by downstream systems.

### Why package nerds care

For package nerds, oslo is a good example of a standards-adjacent CLI: the binary matters less than the schema discipline it enforces. Packaging it gives SRE teams a reproducible validator for reliability metadata in the same way formatters and linters gate application code.

### Timeline

- 2021-04-27: the OpenSLO specification repository is created.
- 2021-04-30: the oslo CLI repository is created.
- 2025-06-29: oslo v0.13.0 is published on GitHub Releases.

### Related projects

- The OpenSLO specification is the parent standard. OpenSLO/slogen is a related project that turns OpenSLO configs into dashboards, monitors, SLI data, and Terraform-oriented output.

### Sources

- <https://api.github.com/repos/OpenSLO/OpenSLO>
- <https://api.github.com/repos/OpenSLO/oslo>
- <https://api.github.com/repos/OpenSLO/oslo/releases?per_page=5>
- <https://formulae.brew.sh/formula/oslo>
- <https://github.com/OpenSLO/OpenSLO>
- <https://github.com/OpenSLO/oslo/blob/main/README.md>
- <https://openslo.com/>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/oslo.yml](https://github.com/mxcl/pkgdb/blob/main/combined/oslo.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph