Automic VaultAutomic Vault

brew

ignite mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ignite in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ignite

local Homebrew formula metadata

Überblick

Paketzusammenfassung

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

Befehle und Aliase

  • ignite

Verlauf

Projektgeschichte und Nutzung

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`.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 2 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ignitecliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version29.10.1
Manager aktualisiert2026-06-16
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv29.10.1

https://github.com/ignite/cli

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ignite
Version29.10.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ignite
Homepagehttps://docs.ignite.com/
Repositoryhttps://github.com/ignite/cli
Upstream-Dokumentationhttps://docs.ignite.com/
LizenzApache-2.0
Quellarchivhttps://github.com/ignite/cli/archive/refs/tags/v29.10.1.tar.gz
Zuletzt aktualisiert2026-06-16T17:57:55Z
Pulseupdated
Abhängigkeitengo, node
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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