Automic VaultAutomic Vault

brew

使用 Homebrew 安装 nifi-registry

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

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install nifi-registry

local Homebrew formula metadata

概览

软件包摘要

Centralized storage & management of NiFi/MiNiFi shared resources

命令和别名

  • nifi-registry

历史

项目历史与用法

Apache NiFi Registry is a NiFi subproject for storing and managing shared resources, especially versioned NiFi flows. It is best understood as a companion service to Apache NiFi rather than a standalone data platform.

项目历史

NiFi Registry grew out of the Apache NiFi ecosystem after NiFi entered Apache from NSA's NiagaraFiles work. The Registry page describes it as a complementary application for storage and management of shared resources across one or more NiFi or MiNiFi instances.

The first Registry implementation focused on versioned flows: process-group-level dataflows created in NiFi could be placed under version control, organized into buckets, and managed through Registry permissions.

采用历史

Registry adoption followed NiFi teams that needed repeatable flow promotion, rollback, and collaboration. The official user guide centers on buckets, flows, versions, changelogs, import/export, user/group management, and policies.

The adoption story changed with NiFi 2. The official Registry page says Apache NiFi Registry was deprecated after a February 2026 community vote and is planned for removal in Apache NiFi 3.0 because NiFi 2 introduced Git-based Flow Registry Clients for GitHub, GitLab, Bitbucket, and Azure DevOps.

Homebrew's formula API reported 210 installs over 365 days, 57 over 90 days, and 22 over 30 days when queried on July 1, 2026. That smaller count compared with nifi itself fits a companion service used mainly by teams doing flow versioning.

使用方式

Operators used NiFi Registry to create buckets, store versioned flows, inspect the change log for saved versions, export a flow version, import a new version, and control permissions around those artifacts. In NiFi 1.x style deployments, it was the dedicated service for flow version control.

Package nerds usually install it alongside nifi and nifi-toolkit for local labs or automation tests: run the Registry service, point NiFi at it as a registry client, then use either the web UI or toolkit CLI commands to import/export or promote flows.

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

The interesting packaging wrinkle is lifecycle. nifi-registry packages a real historical NiFi deployment pattern, but the official project direction has moved toward direct Git-based flow registry clients in NiFi 2. That makes the formula useful context for older installations and migration work.

时间线

  • November 25, 2014: NSA announces the open-source release of NiagaraFiles/NiFi through Apache.
  • July 20, 2015: Apache announces NiFi as a Top-Level Project.
  • NiFi 1.x era: Registry serves as the dedicated service for versioned flows.
  • February 2026: Apache NiFi Registry is deprecated after a community vote, according to the Registry project page.
  • Apache NiFi 3.0: Registry is planned for removal unless maintenance circumstances change.

Related projects

  • Apache NiFi, Apache MiNiFi, NiFi Toolkit, GitHub Flow Registry Client, GitLab Flow Registry Client, Bitbucket Flow Registry Client, Azure DevOps Flow Registry Client

安全态势

风险级别:绿色

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 元数据适用于 1 个平台目标。
  • 安装时包含 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
$NIFI_REGISTRY_HOME/conf/nifi-registry.properties$NIFI_REGISTRY_HOME/conf/bootstrap.conf$NIFI_REGISTRY_HOME/conf/identity-providers.xml$NIFI_REGISTRY_HOME/conf/authorizers.xml

可执行文件

已安装的可执行文件

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

新鲜度

版本和新鲜度

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

页面生成时间2026-07-25
管理器版本2.10.0
管理器更新时间2026-06-19
本地数据OK
上游not checked
检测到的最新版本未检测到

https://nifi.apache.org/projects/registry

安装元数据

软件包元数据

软件包键brew:nifi-registry
版本2.10.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/nifi-registry
主页https://nifi.apache.org/projects/registry
仓库https://github.com/apache/nifi
上游文档https://nifi.apache.org/docs/nifi-registry-docs
许可证Apache-2.0
源码归档https://www.apache.org/dyn/closer.lua?path=/nifi/2.10.0/nifi-registry-2.10.0-bin.zip
最后更新2026-06-19T07:47:05Z
Pulseupdated
依赖openjdk
Bottle可用 (于 all)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

来源线索

由仓库数据生成

此页面由 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
  • package relationship graph
  • package version freshness
  • package-page enrichment