Automic VaultAutomic Vault

brew

Install ignite with Homebrew

Build, launch, and maintain any crypto application with Ignite CLI. Version 29.10.1 via Homebrew; verified 2026-06-16.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install ignite

local Homebrew formula metadata

overview

Package summary

Build, launch, and maintain any crypto application with Ignite CLI

Commands and aliases

  • ignite

history

Project history and usage

Ignite CLI is a Go command-line tool for scaffolding, running, and maintaining Cosmos SDK application blockchains. It packages a large amount of Cosmos boilerplate into commands such as `ignite scaffold chain` and `ignite chain serve`.

Project history

The repository was created in 2020 and built its early identity around fast application-chain scaffolding for the Cosmos ecosystem. The project later moved through a Starport-to-Ignite rebrand; an official issue from April 2022 tracks replacing Starport naming with Ignite and Ignite CLI across docs and commands.

The README frames Ignite CLI as a developer-friendly interface to Cosmos SDK and records a compatibility table that ties Ignite versions to Cosmos SDK and IBC versions. That table is part of the tool's history: as Cosmos SDK evolved, Ignite became not just a generator but also a version-aligned workflow tool for chain developers.

Adoption history

Ignite's adoption is tied to Cosmos SDK education and bootstrapping. The official tutorials present Ignite as the starting point for a first Cosmos blockchain, while the README documents Homebrew, Snap, manual installation, GitHub Discussions, and a bounty/contribution process around the CLI.

How it is used

The canonical workflow is to install the binary, run `ignite scaffold chain <name>`, enter the generated project, and run `ignite chain serve`. Follow-on scaffold commands create modules, messages, queries, and app structure while preserving placeholder markers so generated code can continue to be extended.

Why package nerds care

Ignite is significant because it exposes blockchain-framework churn directly as package metadata and generated code. For package maintainers, the CLI's value depends on matching Go, Cosmos SDK, IBC, and generated project layouts, which is why the version compatibility table matters as much as the executable itself.

Timeline

  • 2020: Public GitHub releases began under the Starport-era project lineage.
  • 2022: The project tracked a Starport-to-Ignite rebrand across source and docs.
  • 2022: Ignite CLI v0.23.0 aligned with Cosmos SDK v0.45.5 and IBC v3.0.1.
  • 2024: Version 28 introduced support for Cosmos SDK v0.50 and v0.53 lines.
  • 2025: Version 29 continued the v0.50/v0.53 compatibility line and IBC v10.2.0 support.

Related projects

  • Ignite is closely related to Cosmos SDK, IBC, Tendermint/CometBFT-era chain development, the Ignite Apps marketplace, and the generated web/front-end templates referenced by the project docs.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 2 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
ignitecliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version29.10.1
manager updated2026-06-16
local dataok
upstreamcurrent
latest detectedv29.10.1

https://github.com/ignite/cli

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:ignite
Version29.10.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/ignite
Homepagehttps://docs.ignite.com/
Repositoryhttps://github.com/ignite/cli
Upstream docshttps://docs.ignite.com/
LicenseApache-2.0
Source archivehttps://github.com/ignite/cli/archive/refs/tags/v29.10.1.tar.gz
Last updated2026-06-16T17:57:55Z
Pulseupdated
Dependenciesgo, node
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameignite
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment