Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 firefly

查看 firefly 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install firefly

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#firefly

nixpkgs package indexes · pkgs/by-name/fi/firefly/package.nix · 来源: api.github.com

概览

软件包摘要

Create and manage the Hyperledger FireFly stack for blockchain interaction

命令和别名

  • firefly

历史

项目历史与用法

Hyperledger FireFly CLI is the local stack-management tool for Hyperledger FireFly, an open-source Web3 application stack. The CLI creates and manages local FireFly stacks so developers can build blockchain applications without manually assembling Docker, blockchain connectors, FireFly Core, Explorer, Sandbox, and supporting services.

项目历史

The firefly-cli repository was created in May 2021. Its README frames the tool as a way to create local FireFly stacks for offline blockchain app development, letting developers iterate before setting up production infrastructure.

FireFly itself is described by the official core repository as an open-source Supernode: a complete stack for enterprises to build and scale secure Web3 applications. The CLI is one piece of that ecosystem, alongside FireFly Core, Explorer, Sandbox, SDKs, blockchain connectors, token connectors, samples, and Helm charts.

采用历史

The CLI's adoption is intentionally developer-local. Official docs tell users to install Docker, Docker Compose, and openssl, then install the CLI via release binaries, Homebrew, or Go. That makes it a bootstrapper for trying FireFly rather than a production runtime by itself.

In the FireFly documentation, the CLI appears as one of the main tools next to FireFly Sandbox and FireFly Explorer. That position matters: the CLI is the shortest path from package installation to a running local network of FireFly Supernodes.

使用方式

Users create a stack with `ff init <stack_name>`, start it with `ff start <stack_name>`, inspect logs with `ff logs`, stop it with `ff stop`, reset data with `ff reset`, remove it with `ff remove`, inspect it with `ff info`, and list stacks with `ff ls`.

The CLI is used when developers need an offline or local FireFly environment for blockchain app work. It hides much of the underlying service wiring while still leaving stack configuration and Docker Compose artifacts available for advanced customization.

为什么软件包爱好者会关心

FireFly CLI is package-interesting because it is a Go-distributed executable that bootstraps a multi-service blockchain development environment. Installing a small CLI gives users a reproducible local stack rather than just another client binary.

It also captures a broader packaging pattern in cloud and Web3 tools: the package manager installs the orchestrator, and the orchestrator materializes Docker-based services, generated configuration, local credentials, UI tools, and protocol connectors.

时间线

  • 2021: firefly-cli repository is created on GitHub.
  • 2021: Early GitHub releases publish precompiled CLI artifacts.
  • 2020s: Official FireFly docs position the CLI beside Sandbox and Explorer as a core developer tool.
  • 2026: Repository metadata shows continued firefly-cli maintenance activity.

Related projects

  • Hyperledger FireFly Core is the main runtime and orchestration engine that the CLI helps run locally.
  • FireFly Explorer and FireFly Sandbox are the companion developer tools surfaced in official docs.
  • FireFly transaction manager, signer, EVM, Fabric, Tezos, Cardano, token, data-exchange, SDK, samples, and Helm chart repositories are neighboring pieces of the FireFly ecosystem.
  • Docker and Docker Compose are required local dependencies for running CLI-managed stacks.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 1 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

local files

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

Config paths the tool may read or write during local use.

Unix
~/.firefly/stacks/<stack_name>/runtime/config/firefly_core_0.yml~/.firefly/stacks/<stack_name>/docker-compose.override.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
test_users

可执行文件

已安装的可执行文件

命令类型暴露范围备注
fireflycli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-08
管理器版本1.4.0
管理器更新时间2026-07-04
本地数据OK
上游当前
检测到的最新版本v1.4.0

https://github.com/hyperledger-firefly/cli

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:firefly
版本1.4.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/firefly
主页https://hyperledger.github.io/firefly/latest/
仓库https://github.com/hyperledger-firefly/cli
上游文档https://github.com/hyperledger/firefly-cli#readme
许可证Apache-2.0
源码归档https://github.com/hyperledger-firefly/cli/archive/refs/tags/v1.4.0.tar.gz
最后更新2026-07-04T16:53:42+09:00
Pulseupdated
构建依赖go
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

firefly

nix profile install nixpkgs#firefly
  • normalized package name match
  • 匹配方式:Firefly
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fi/firefly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment