# Install flow with Homebrew, MacPorts, Nix, scoop, winget Static type checker for JavaScript. Version 0.325.0 via Homebrew; verified 2026-07-30. Also installable with nix: nix profile install nixpkgs#flow. ## Install ```sh sudo av install brew:flow ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install flow ``` Evidence: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install flow ``` Evidence: 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 ``` Evidence: 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 ``` Evidence: 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 ``` Evidence: Windows Package Manager source index: MadrasCheck.flow from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:flow - **Package manager:** Homebrew - **Version:** 0.325.0 - **Source summary:** Static type checker for JavaScript - **Homepage:** - **Repository:** - **Last updated:** 2026-07-30T03:22:19Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - flow (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.325.0 ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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. ### Sources - - - - - ## Security Notes No matching local secret-handling manifest was found for flow. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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 ## Other Package-Manager Records - 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) ## Sources - 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