pkg.soopen package index

brew / rank 2222

Install vapor with Homebrew, MacPorts

Command-line tool for Vapor (Server-side Swift web framework). Version 20.0.2 via Homebrew; verified 2026-07-31. Also installable with macports: sudo port install vapor.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install vapor

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install vapor

MacPorts ports tree · science/vapor/Portfile · source: api.github.com

overview

Package summary

Command-line tool for Vapor (Server-side Swift web framework)

Commands and aliases

  • vapor

history

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.

security posture

Risk level: blue

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

Risk classifier

blue risk · medium confidence · tool

Why

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

Signals

  • text:server

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
vaporexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version20.0.2
manager updated2026-07-31
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:vapor
Version20.0.2
Package managerHomebrew
Homepagehttps://vapor.codes
Repositoryhttps://github.com/vapor/toolbox
Last updated2026-07-31T13:41:16Z
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

vapor

sudo port install vapor
  • normalized package name match
  • Matched by: Vapor
MacPorts ports tree · api.github.com · MacPorts ports tree: science/vapor/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation