# nifi を Homebrew, Nix でインストール nifi のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:nifi ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install nifi ``` 証拠: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#nifi ``` 証拠: nixpkgs package indexes: pkgs/by-name/ni/nifi/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## パッケージ情報 - **パッケージキー:** brew:nifi - **パッケージマネージャ:** Homebrew - **バージョン:** 2.11.0 - **ソース概要:** Easy to use, powerful, and reliable system to process and distribute data - **ホームページ:** - **最終更新:** 2026-08-03T15:05:41Z - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - nifi (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 2.11.0 ## プロジェクトの歴史と使われ方 Apache NiFi is a visual, extensible system for automating data movement between systems. It combines a browser-based flow designer, back pressure, guaranteed delivery options, security controls, and data provenance so operators can design and monitor dataflow graphs. ### プロジェクトの歴史 NiFi began inside the U.S. National Security Agency as NiagaraFiles. NSA announced the public open-source release on November 25, 2014, saying the tool automated data flows among networks even when formats and protocols differed. The Apache Software Foundation later described the donated system as having more than eight years of closed-source development before its Apache transition. Apache announced NiFi as a Top-Level Project on July 20, 2015. The ASF announcement emphasized flow-based programming, a web UI for designing and controlling flows, fine-grained data provenance, security, scalability, and an extension model with integrations such as FTP, SFTP, HTTP, and HDFS. NiFi 2.0.0 reached general availability on November 4, 2024, according to Apache release notes. That release opened the 2.x line after milestone releases and included new capabilities such as GitLab flow registry client integration, new S3/SFTP processors, REST API services for assets and custom bundles, and a larger modernization path. ### 採用の歴史 NiFi's adoption is enterprise-dataflow adoption: it is used where teams need to move, transform, route, observe, and replay data between systems with operational visibility. The NiFi homepage says it automates cybersecurity, observability, event streams, and generative AI data pipelines for thousands of companies worldwide. Its ecosystem includes the main NiFi application, MiNiFi, NiFi Registry, the Toolkit, many processors, and commercial distributions/support from vendors in the Apache data stack. The original ASF announcement quoted Hortonworks, Prescient Edge, and Leverege leaders describing NiFi integration and adoption use cases. Homebrew's formula API reported 1,131 installs over 365 days, 198 over 90 days, and 76 over 30 days when queried on July 1, 2026. For a large Java server normally deployed on Linux or Kubernetes, that Homebrew count is best read as local development and evaluation usage, not total adoption. ### 使われ方 Developers and operators use NiFi by starting the service, opening the web UI, dragging processors onto a canvas, connecting them with queues, configuring controller services and parameters, then monitoring throughput, back pressure, failures, and provenance. It is commonly used for ETL-like data movement, ingest pipelines, event routing, file transfer automation, and integration between legacy and modern systems. Package nerd usage on macOS is usually local evaluation, processor development, tutorial work, or reproducing a flow before deploying to a server environment. The package is large and service-like, so serious deployments usually move beyond a local Homebrew install into managed Linux, containers, or platform-specific operations. ### パッケージ好きにとっての重要性 NiFi is significant because it packages a GUI-first dataflow runtime into a reproducible open-source distribution. For package metadata, it is also a good example of a project whose formula only captures one surface of a larger ecosystem: nifi, nifi-toolkit, nifi-registry, Maven artifacts, processors, Docker/Kubernetes patterns, and vendor distributions all matter. ### タイムライン - 2006-2014: ASF later describes NiFi/NiagaraFiles as having more than eight years of development before Apache incubation. - November 25, 2014: NSA announces NiagaraFiles/NiFi as an open-source release through Apache. - November 2014: NiFi is submitted to the Apache Incubator as part of the NSA Technology Transfer Program. - July 20, 2015: Apache NiFi graduates to an Apache Top-Level Project. - November 4, 2024: Apache NiFi 2.0.0 is released as the first general availability version of the 2.x line. - January 27, 2025: Apache release notes list NiFi 2.2.0 as a feature improvement and bug fix release. ### Related projects - Apache NiFi Registry, Apache NiFi Toolkit, Apache MiNiFi, Apache Kafka, Apache Hadoop, Apache Spark, HDFS ### ソース - - - - - - ## セキュリティノート narrow executable package without higher-risk signals. - **Geiger リスク:** グリーン / 低 - 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: $NIFI_HOME/conf/nifi.properties, $NIFI_HOME/conf/bootstrap.conf, $NIFI_HOME/conf/flow.xml.gz, $NIFI_HOME/conf/login-identity-providers.xml, $NIFI_HOME/conf/authorizers.xml ## 他のパッケージマネージャ記録 - Nix - nifi: normalized package name match | nixpkgs package indexes: pkgs/by-name/ni/nifi/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/nifi.yml](https://github.com/mxcl/pkgdb/blob/main/combined/nifi.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph