Automic VaultAutomic Vault

brew

Install swagger-codegen with Homebrew, MacPorts, Nix

Generate clients, server stubs, and docs from an OpenAPI spec. Version 3.0.81 via Homebrew; verified 2026-05-18.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install swagger-codegen

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install swagger-codegen

MacPorts ports tree · devel/swagger-codegen/Portfile · source: api.github.com

Linux

Nixverified · 92%
nix profile install nixpkgs#swagger-codegen

nixpkgs package indexes · pkgs/by-name/sw/swagger-codegen/package.nix · source: api.github.com

overview

Package summary

Generate clients, server stubs, and docs from an OpenAPI spec

Commands and aliases

  • swagger-codegen

history

Project history and usage

Swagger Codegen is the Swagger/OpenAPI project's command-line code generator for API clients, server stubs, and documentation. The Homebrew `swagger-codegen` formula tracks the modern 3.x line, which adds OpenAPI 3.0 support while sharing the long-running upstream repository.

Project history

The swagger-api/swagger-codegen repository was created on GitHub in July 2011. Official Swagger documentation describes Swagger Codegen as a project that generates API client libraries, server stubs, and documentation automatically from an OpenAPI Description.

Adoption history

Swagger Codegen became widely packaged because it is a single Java CLI that can generate code for many languages and frameworks. The official README lists client generators for languages including Java, Go, Python, Ruby, PHP, Swift, TypeScript, and many others, plus server stubs and documentation outputs.

How it is used

The common CLI pattern is to run the codegen jar with `generate`, pass an input spec with `-i`, select a target language with `-l`, and choose an output directory with `-o`. Official docs also describe querying generator capabilities and integrating generation into Maven, Gradle, Docker, GitHub, and CI workflows.

Why package nerds care

For package-manager users, Swagger Codegen is important because it converts API descriptions into language-specific source trees without requiring each language ecosystem to maintain its own generator. It is also a classic example of a large Java CLI distributed through system package managers, Maven artifacts, Docker, and release jars.

Timeline

  • 2011: GitHub repository created.
  • 2014: v2.0.13 appears in GitHub releases.
  • 2018: v3.0.0 released with the 3.x line.
  • 2025: Official docs list 3.0.71 as a stable 3.x release with OpenAPI 3.0 compatibility.
  • 2026: GitHub releases list later 3.x releases during research.

Related projects

  • The official docs tie Swagger Codegen to the OpenAPI Specification and Swagger tooling. The README also points to Swagger online generators, a validator, and workflow integrations.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for swagger-codegen. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.
  • Build metadata lists 1 build dependencies.

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
swagger-codegencliglobal executable

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-07-08
manager version3.0.81
manager updated2026-05-18
local dataok
upstreamcurrent
latest detectedv3.0.81

https://github.com/swagger-api/swagger-codegen

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:swagger-codegen
Version3.0.81
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/swagger-codegen
Homepagehttps://swagger.io/tools/swagger-codegen/
Repositoryhttps://github.com/swagger-api/swagger-codegen
Upstream docshttps://github.com/swagger-api/swagger-codegen#readme
LicenseApache-2.0
Source archivehttps://github.com/swagger-api/swagger-codegen/archive/refs/tags/v3.0.81.tar.gz
Last updated2026-05-18T14:26:15Z
Pulseupdated
Dependenciesopenjdk
Build dependenciesmaven
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameswagger-codegen
Aliases
  • swagger-codegen@3
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

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

Nix95%

swagger-codegen

nix profile install nixpkgs#swagger-codegen
  • normalized package name match
  • Matched by: Swagger Codegen
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/sw/swagger-codegen/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

swagger-codegen

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

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
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment