# flow mit Homebrew, MacPorts, Nix, scoop, winget installieren

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

## Installation

```sh
sudo av install brew:flow
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install flow
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install flow
```

  Evidenz: MacPorts ports tree: devel/flow/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#flow
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/fl/flow/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Scoop (92%):

```sh
scoop install main/flow
```

  Evidenz: Scoop official bucket manifest trees: bucket/flow.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id MadrasCheck.flow -e
```

  Evidenz: Windows Package Manager source index: MadrasCheck.flow from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:flow
- **Paketmanager:** Homebrew
- **Version:** 0.325.0
- **Quellzusammenfassung:** Static type checker for JavaScript
- **Homepage:** <https://flow.org/>
- **Repository:** <https://github.com/facebook/flow>
- **Zuletzt aktualisiert:** 2026-07-30T03:22:19Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- flow (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.325.0
## Projektgeschichte und Nutzung

Flow is Meta's static type checker and typed JavaScript dialect, distributed as the flow CLI and related npm tooling for checking JavaScript programs before runtime.

### Projektgeschichte

Facebook announced Flow in November 2014 as a new static type checker for JavaScript designed to find errors by analyzing programs without running them. The official repository describes Flow as a static typechecker for JavaScript and points users to flow.org for documentation.

Flow developed around a per-project configuration file, .flowconfig, and an npm-oriented setup through flow-bin. Its documentation also covers Babel and flow-remove-types for stripping Flow type annotations before publishing or running JavaScript.

### Adoptionsgeschichte

Flow became closely associated with Facebook and React-era JavaScript projects, where static analysis was adopted to make large JavaScript codebases easier to maintain. The official docs include React-specific material and a dedicated guide for TypeScript users, reflecting Flow's long-running position in the JavaScript type-checking ecosystem.

In 2023, the Flow team published an official direction statement explaining that the project was focusing on Meta's internal use cases and would reduce broad open-source engagement, a notable shift in the project's adoption story.

### Wie es verwendet wird

Typical usage is project-local: install flow-bin, add a flow script, run flow init to create .flowconfig, and run flow to type-check source files. Flow projects use type annotations in JavaScript source and a compiler such as Babel or flow-remove-types to remove those annotations for runtime JavaScript.

Flow also publishes parser tooling, including flow-parser, for packages that need to parse Flow-typed JavaScript directly.

### Warum Paket-Nerds sich dafür interessieren

Flow matters to package maintainers because it is both a CLI and a language-extension ecosystem: packages may ship Flow annotations, require stripping transforms, pin flow-bin versions, or expose libdefs and parser behavior that differ across releases.

Its history is also a useful contrast point for TypeScript in package metadata, because Flow-heavy projects often leave signals such as .flowconfig, flow-bin dev dependencies, and type-stripping build scripts.

### Zeitleiste

- 2014: Facebook announces Flow as a static type checker for JavaScript.
- 2010s: Flow is used with JavaScript package workflows through flow-bin, Babel, and flow-remove-types.
- 2023: The Flow team states a narrowed open-source direction focused on Meta's internal usage.
- 2026: Official docs show Flow continuing with releases, .flowconfig reference docs, React docs, and TypeScript migration guidance.

### Related projects

- Official docs and README connect Flow to flow-bin, flow-parser, flow-remove-types, Babel, React, and TypeScript migration guidance.

### Quellen

- <https://engineering.fb.com/2014/11/18/web/flow-a-new-static-type-checker-for-javascript/>
- <https://flow.org/en/docs/>
- <https://flow.org/en/docs/config/>
- <https://github.com/facebook/flow>
- <https://medium.com/flow-type/clarity-on-flows-direction-and-open-source-engagement-9bc9c2f4ff65>


## Sicherheitshinweise

Für flow wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## 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: .flowconfig, src/.flowconfig
## Andere Paketmanager-Einträge

- Nix - flow: normalized package name match | nixpkgs package indexes: pkgs/by-name/fl/flow/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- MacPorts - flow: normalized package name match | MacPorts ports tree: devel/flow/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Scoop - main/flow: normalized package name match | Scoop official bucket manifest trees: bucket/flow.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - MadrasCheck.flow: normalized package name match | Windows Package Manager source index: MadrasCheck.flow from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/flow.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flow.yml)


## Quellen

- 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