Automic VaultAutomic Vault

brew

nifi mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install nifi

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#nifi

nixpkgs package indexes · pkgs/by-name/ni/nifi/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Easy to use, powerful, and reliable system to process and distribute data

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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

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 1 Plattformziele verfügbar.
  • Installiert mit 1 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.

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_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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
nificliglobales 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-Version2.10.0
Manager aktualisiert2026-06-19
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://nifi.apache.org

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:nifi
Version2.10.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/nifi
Homepagehttps://nifi.apache.org
Repositoryhttps://github.com/apache/nifi
Upstream-Dokumentationhttps://nifi.apache.org/components
LizenzApache-2.0
Quellarchivhttps://www.apache.org/dyn/closer.lua?path=/nifi/2.10.0/nifi-2.10.0-bin.zip
Zuletzt aktualisiert2026-06-19T07:56:55Z
Pulseupdated
Abhängigkeitenopenjdk@21
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

nifi

nix profile install nixpkgs#nifi
  • normalized package name match
  • Abgeglichen nach: Nifi
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ni/nifi/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment