# Installer vapor avec Homebrew, MacPorts Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vapor pour les workflows d'agents IA. ## installation ```sh sudo av install brew:vapor ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install vapor ``` Preuve: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install vapor ``` Preuve: MacPorts ports tree: science/vapor/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Faits du paquet - **Clé du paquet:** brew:vapor - **Gestionnaire de paquets:** Homebrew - **Version:** 20.0.2 - **Résumé source:** Command-line tool for Vapor (Server-side Swift web framework) - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-31T13:41:16Z - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - vapor (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 20.0.2 ## Historique du projet et usages 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. ### Historique du projet 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. ### Historique d'adoption 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. ### Modes d'utilisation 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 - - - - - ## Notes de sécurité broad file, network, media, or database tool signal. - **Risque Geiger:** blue / moyen - broad file, network, media, or database tool signal ## Autres enregistrements de gestionnaires de paquets - 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 ## Combined YAML source View the package source record on GitHub. [combined/vapor.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vapor.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph