# 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 - **Package manager page:** - **Version:** 2.8.2 - **Source summary:** API Testing and Monitoring made simple - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MPL-2.0 - **Source archive:** - **Generated:** 2026-07-08T18:08:21+00:00 ## Executables - stepci (cli) - stepci (alias) ## Dependencies - node ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.8.2 - Local data: ok - Upstream repository: https://stepci.com - info: No package-manager update timestamp was available. - info: Release/tag comparison is only available for GitHub repositories. ## 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 - - - - - - - - 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 ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** stepci - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew. - [allure](https://www.automicvault.com/pkg/brew/allure/) - Shares av.db curated category or tags: cli, developer-tools, qa, testing. - [buildpulse-test-reporter](https://www.automicvault.com/pkg/brew/buildpulse-test-reporter/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [cargo-nextest](https://www.automicvault.com/pkg/brew/cargo-nextest/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [chart-testing](https://www.automicvault.com/pkg/brew/chart-testing/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [flank](https://www.automicvault.com/pkg/brew/flank/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [gotestsum](https://www.automicvault.com/pkg/brew/gotestsum/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [keploy](https://www.automicvault.com/pkg/brew/keploy/) - Shares av.db curated category or tags: api-testing, cli, developer-tools, testing. - [nox](https://www.automicvault.com/pkg/brew/nox/) - Shares av.db curated category or tags: ci, cli, developer-tools, testing. - [newman](https://www.automicvault.com/pkg/brew/newman/) - Both packages touch the same language runtime or ecosystem. Shared terms: api, api-testing, ci, cli, developer. - [bruno-cli](https://www.automicvault.com/pkg/brew/bruno-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: api, api-testing, cli, developer, developer-tools. - [prism-cli](https://www.automicvault.com/pkg/brew/prism-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: api, cli, developer, developer-tools, node. ## Combined YAML source View the package source record on GitHub. [combined/stepci.yml](https://github.com/automic-vault/db/blob/main/combined/stepci.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph