# Install faas-cli with Homebrew, chocolatey, Nix, scoop

CLI for templating and/or deploying FaaS functions. Version 0.18.10 via Homebrew; verified 2026-06-16.

## Install

```sh
sudo av install brew:faas-cli
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install faas-cli
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#faas-cli
```

  Evidence: nixpkgs package indexes: pkgs/by-name/fa/faas-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Chocolatey (92%):

```sh
choco install faas-cli
```

  Evidence: Chocolatey community package catalog: faas-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='8.6352005','msys2-installer'

- Scoop (92%):

```sh
scoop install main/faas-cli
```

  Evidence: Scoop official bucket manifest trees: bucket/faas-cli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:faas-cli
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/faas-cli>
- **Version:** 0.18.10
- **Source summary:** CLI for templating and/or deploying FaaS functions
- **Homepage:** <https://www.openfaas.com/>
- **Repository:** <https://github.com/openfaas/faas-cli>
- **Upstream docs:** <https://docs.openfaas.com/cli/install>
- **License:** MIT
- **Source archive:** <https://github.com/openfaas/faas-cli/archive/refs/tags/0.18.10.tar.gz>
- **Last updated:** 2026-06-16T21:53:29Z
- **Generated:** 2026-07-08T18:08:21+00:00

## Executables

- faas (cli)
- faas-cli (cli)
- faas (alias)
- faas-cli (alias)

## Build dependencies

- go

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 0.18.10
- Package-manager updated: 2026-06-16
- Local data: ok
- Upstream repository: https://github.com/openfaas/faas-cli
- Upstream latest detected: 0.18.10 (current)
## Project history and usage

faas-cli is the official command-line interface for OpenFaaS, used to create, build, push, deploy, invoke, and manage serverless functions.

### Project history

The faas-cli repository was created in April 2017 as the OpenFaaS command-line entry point. The project README describes it as the official CLI for OpenFaaS and explains the original core workflow: write a handler, pick a language template, and let the CLI build a Docker image and deploy the function.

As OpenFaaS matured, faas-cli became the stable user-facing tool around a broader platform. Its command set grew from the basic new, build, push, deploy, remove, and invoke lifecycle into template stores, secrets, registry login, multi-arch publishing, and OpenFaaS Pro authentication flows.

The CLI also reflects OpenFaaS's packaging strategy. Official installation docs support a curl installer, Homebrew, Windows binaries, Chocolatey, Scoop, and direct release downloads, so the same tool fits local demos, CI pipelines, and workstation use.

### Adoption history

OpenFaaS adoption made faas-cli important because nearly every getting-started path goes through it. The README shows Homebrew installation, a `faas` alias, and commands for creating functions from templates, while the official install docs document cross-platform packaging for macOS, Linux, and Windows.

The CLI's adoption is tied to the OpenFaaS gateway model: developers log in to a gateway, point the CLI at `OPENFAAS_URL` or a gateway flag, then deploy function definitions from YAML. That made it a bridge between local source trees, Docker registries, and Kubernetes or other OpenFaaS providers.

### How it is used

Typical use starts with `faas-cli new` to scaffold a function from a language template, then `faas-cli up` as the shorthand for build, push, and deploy. Operators use `faas-cli login`, `secret`, `store`, `invoke`, `remove`, and gateway flags or environment variables to work with local or remote OpenFaaS installations.

The CLI is also a packaging surface for templates. Official docs describe pulling templates from remote Git repositories and using a template store for official, incubator, and community templates, which is why the tool matters beyond simply sending API calls to a gateway.

### Why package nerds care

For package people, faas-cli is a clean example of a Go-based cloud CLI distributed through many channels while keeping a curl installer and release binaries as the canonical path. It also carries the familiar package-manager tension noted by its README: Homebrew is updated regularly, but may not always be the newest minor release.

Its command alias matters too. Installing the package gives both `faas-cli` and `faas`, which is the sort of executable naming detail that package formulas, shell completions, and docs all have to keep aligned.

### Timeline

- 2017: The faas-cli repository is created as the OpenFaaS CLI.
- 2020: The CLI includes release entries for list output improvements and gateway/provider serialization updates.
- 2021: Release entries add registry-login and secrets whitespace handling.
- 2026: The README continues to document core build, deploy, template, secret, publish, and Pro auth commands.

### Related projects

- OpenFaaS is the serverless platform that faas-cli targets.
- openfaas/templates provides the default language templates used by `faas-cli new` and `faas-cli template pull`.

### Sources

- <https://api.github.com/repos/openfaas/faas-cli>
- <https://github.com/openfaas/faas-cli>
- <https://github.com/openfaas/faas-cli/blob/master/README.md>
- <https://docs.openfaas.com/cli/install>
- <https://github.com/openfaas/faas-cli/releases>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- 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.


## Credential files

- Unix: ~/.openfaas/config.yml, .openfaas/config.yml
## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** faas-cli
- **Aliases:** faas
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable

## Other Package-Manager Records

- Nix - faas-cli: normalized package name match | nixpkgs package indexes: pkgs/by-name/fa/faas-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Chocolatey - faas-cli: normalized package name match | Chocolatey community package catalog: faas-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='8.6352005','msys2-installer'
- Scoop - main/faas-cli: normalized package name match | Scoop official bucket manifest trees: bucket/faas-cli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Related links

- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew.
- [cloudflare-wrangler](https://www.automicvault.com/pkg/brew/cloudflare-wrangler/) - Shares av.db curated category or tags: cli, deployment, developer-tools, serverless.
- [cartridge-cli](https://www.automicvault.com/pkg/brew/cartridge-cli/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [deployer](https://www.automicvault.com/pkg/brew/deployer/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [doubledown](https://www.automicvault.com/pkg/brew/doubledown/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [dylibbundler](https://www.automicvault.com/pkg/brew/dylibbundler/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [fabric](https://www.automicvault.com/pkg/brew/fabric/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [fastlane](https://www.automicvault.com/pkg/brew/fastlane/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [git-ftp](https://www.automicvault.com/pkg/brew/git-ftp/) - Shares av.db curated category or tags: cli, deployment, developer-tools.
- [langgraph-cli](https://www.automicvault.com/pkg/brew/langgraph-cli/) - Local package facts share a topical domain. Shared terms: cli, deploying, deployment, developer, developer-tools.

## Combined YAML source

View the package source record on GitHub. [combined/faas-cli.yml](https://github.com/automic-vault/db/blob/main/combined/faas-cli.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
