# Install vapor with Homebrew, MacPorts

Command-line tool for Vapor (Server-side Swift web framework). Version 20.0.0 via Homebrew; verified 2026-05-10.

## Install

```sh
sudo av install brew:vapor
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install vapor
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install vapor
```

  Evidence: MacPorts ports tree: science/vapor/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:vapor
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/vapor>
- **Version:** 20.0.0
- **Source summary:** Command-line tool for Vapor (Server-side Swift web framework)
- **Homepage:** <https://vapor.codes>
- **Repository:** <https://github.com/vapor/toolbox>
- **Upstream docs:** <https://docs.vapor.codes/getting-started/hello-world>
- **License:** MIT
- **Source archive:** <https://github.com/vapor/toolbox/archive/refs/tags/20.0.0.tar.gz>
- **Last updated:** 2026-05-10T22:45:31-04:00
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- vapor (cli)
- vapor (alias)

## Install behavior

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

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 20.0.0
- Package-manager updated: 2026-05-10
- Local data: ok
- Upstream repository: https://github.com/vapor/toolbox
- Upstream latest detected: 20.0.0 (current)
## Project history and usage

The Homebrew `vapor` package is the Vapor Toolbox, the command-line companion to Vapor, a server-side Swift web framework. Vapor emerged in the first wave of server-side Swift after Apple open sourced Swift and Linux support in December 2015. Secondary histories and GitHub release records place Vapor's early proof-of-concept and 1.0 era in 2016, with Vapor 1.0 in September 2016 and Vapor 2.0 in 2017, as the Swift ecosystem was still learning how much backend work could be done in Swift.

### Project history

A major transition came with Vapor 3.0 in May 2018. Vapor's own release announcement on the Swift forums described Vapor 3 as a ground-up rewrite using Apple's SwiftNIO, shifting the framework toward non-blocking networking and aligning it with the Swift Server Work Group ecosystem. Vapor 4 followed with a stable release in April 2020 and became the long-lived generation documented by current Vapor docs. The core project remains MIT-licensed, hosted on GitHub, and visibly active; the GitHub project page lists more than 26,000 stars and hundreds of releases as of July 2026.

### Adoption history

In package-nerd terms, `brew install vapor` is less about installing a server daemon and more about installing a project generator and workflow helper for Swift backend developers. Typical use is to scaffold a Vapor application, open the generated Swift package in Xcode or another editor, run locally with SwiftPM, and deploy like a normal Swift server process. Its adoption tracks the broader server-side Swift niche: strongest among Swift and iOS developers who want to reuse Swift, Codable models, and Swift tooling on backend APIs.

### How it is used

The toolbox exists to make the framework ergonomic from a terminal. Swift.org's official Vapor web-service guide tells users to install the Vapor toolbox, create a project with `vapor new HelloVapor`, then build and run the generated Swift package. Vapor's docs describe the framework as a way to write backends, web apps, APIs, and HTTP servers in Swift, and its ecosystem includes routing, Codable content handling, Fluent ORM, Leaf templating, Redis support, authentication, queues, WebSockets, deployment guides, and SwiftPM/Xcode workflows.

In package-nerd terms, `brew install vapor` is less about installing a server daemon and more about installing a project generator and workflow helper for Swift backend developers. Typical use is to scaffold a Vapor application, open the generated Swift package in Xcode or another editor, run locally with SwiftPM, and deploy like a normal Swift server process. Its adoption tracks the broader server-side Swift niche: strongest among Swift and iOS developers who want to reuse Swift, Codable models, and Swift tooling on backend APIs.

### Sources

- <https://docs.vapor.codes/>
- <https://en.wikipedia.org/wiki/Vapor_(web_framework)>
- <https://forums.swift.org/t/vapor-3-0-released-ground-up-rewrite-using-swiftnio/12424>
- <https://github.com/vapor/vapor>
- <https://www.swift.org/getting-started/vapor-web-server/>


## Security Notes

broad file, network, media, or database tool signal.

- **Geiger risk:** blue / medium
- broad file, network, media, or database tool signal

## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** vapor
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Requirements:** macos, xcode
- **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

- MacPorts - vapor: normalized package name match | MacPorts ports tree: science/vapor/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Related links

- [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals.
- [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.
- [nuxi](https://www.automicvault.com/pkg/brew/nuxi/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [addons-linter](https://www.automicvault.com/pkg/brew/addons-linter/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [angular-cli](https://www.automicvault.com/pkg/brew/angular-cli/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [commandbox](https://www.automicvault.com/pkg/brew/commandbox/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [cppcms](https://www.automicvault.com/pkg/brew/cppcms/) - Shares av.db curated category or tags: cli, developer-tools, server-side, web-framework.
- [css-crush](https://www.automicvault.com/pkg/brew/css-crush/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [gatsby-cli](https://www.automicvault.com/pkg/brew/gatsby-cli/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [gwt](https://www.automicvault.com/pkg/brew/gwt/) - Shares av.db curated category or tags: cli, developer-tools, web-development.
- [helidon](https://www.automicvault.com/pkg/brew/helidon/) - Local package facts share a topical domain. Shared terms: cli, command-line, developer, developer-tools, development.

## Combined YAML source

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


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- 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
