# Install stepci with Homebrew

API Testing and Monitoring made simple. Version 2.8.2 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:stepci
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install stepci
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:stepci
- **Package manager:** Homebrew
- **Version:** 2.8.2
- **Source summary:** API Testing and Monitoring made simple
- **Homepage:** <https://stepci.com>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- stepci (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Step CI is an open-source API quality-assurance framework packaged as the `stepci` command. It fits package-manager culture as a lightweight test runner for API workflows that can be installed globally and dropped into local development, CI jobs, and monitoring scripts.

### Project history

The stepci/stepci GitHub repository was created in September 2022, and its first listed GitHub release is named 'Step CI goes Open-Source'. The official docs and README describe it as an open-source API QA framework that is language-agnostic and configured with YAML, JSON, or JavaScript.

### Adoption history

Official docs emphasize integration with CI systems and self-hosted execution against local or private-network services. GitHub repository metadata shows a public project with substantial stars for a young API-testing CLI, while the input package-manager facts show Homebrew distribution.

### How it is used

Common usage is writing a workflow file, usually `workflow.yml`, and running it with `stepci run workflow.yml`. The official CLI reference documents `stepci run` for executing workflows and `stepci generate` for generating workflows from OpenAPI specs.

### Why package nerds care

Package nerds care because Step CI packages API smoke tests as a standalone CLI rather than a language-bound test framework. That makes it useful in polyglot repositories and CI environments where a single YAML workflow runner is simpler than wiring separate test dependencies into every service.

### Timeline

- 2022: Public GitHub repository created.
- 2022: Release 1.0.5 published as 'Step CI goes Open-Source'.
- 2024: GitHub releases continued through 2.8.2.
- 2026: Input package facts record Homebrew distribution.

### Related projects

- Step CI relates to OpenAPI tooling, Postman-import workflows, CI systems such as GitHub Actions and GitLab CI, and API protocols including REST, GraphQL, gRPC, tRPC, and SOAP.

### Sources

- <https://api.github.com/repos/stepci/stepci>
- <https://api.github.com/repos/stepci/stepci/releases>
- <https://docs.stepci.com/>
- <https://docs.stepci.com/guides/getting-started.html>
- <https://docs.stepci.com/reference/cli.html>
- <https://docs.stepci.com/reference/workflow-syntax.html>
- <https://github.com/stepci/stepci>
- input.source_facts.package-manager


## Security Notes

narrow executable package without higher-risk signals.

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


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ./workflow.yml
- Windows: .\workflow.yml

## Combined YAML source

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


## Sources

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