Automic VaultAutomic Vault

brew / approval gates

Install xcbeautify with Homebrew, MacPorts, Nix

Little beautifier tool for xcodebuild. Version 3.2.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install xcbeautify

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install xcbeautify

MacPorts ports tree · devel/xcbeautify/Portfile · source: api.github.com

Linux

Nixverified · 92%
nix profile install nixpkgs#xcbeautify

nixpkgs package indexes · pkgs/by-name/xc/xcbeautify/package.nix · source: api.github.com

overview

Package summary

Little beautifier tool for xcodebuild

Commands and aliases

  • xcbeautify

history

Project history and usage

xcbeautify is a Swift command-line formatter for xcodebuild output. Its README presents it as a faster alternative to xcpretty, with colored human-readable output and support for modern Xcode, Swift Package Manager, and CI rendering workflows.

Project history

The GitHub release history shows xcbeautify releases from 0.3.6 in December 2018 to the 3.x series in 2026. The project has remained focused on parsing and presenting Apple's verbose build and test output while tracking changes in Xcode behavior.

The README emphasizes being written in Swift and compiling to a static binary, reducing Ruby dependence in development and CI environments compared with xcpretty. Later features include JUnit report generation and dedicated renderers for GitHub Actions, TeamCity, and Azure DevOps Pipeline.

Adoption history

xcbeautify's adoption is most visible in the iOS and macOS CI ecosystem. fastlane's xcodebuild formatter documentation says fastlane 2.201.0 and later can select an xcodebuild_formatter, defaults to xcbeautify when it is installed, and describes xcbeautify as the recommended formatter.

The same fastlane documentation explains the transition context: xcpretty had historically been tightly integrated with fastlane as a RubyGem dependency, while xcbeautify became preferred for new build-system output, parallel testing output, Swift Package Manager formatting, and speed.

How it is used

The basic usage is to pipe xcodebuild output into xcbeautify. The README also recommends `set -o pipefail` in CI so the pipeline preserves xcodebuild's exit status, and shows unbuffered/combined output for parallel or concurrent destination testing.

CI users can select specialized renderers, such as `--renderer github-actions`, so warnings, errors, and test results appear directly in the CI provider interface instead of only in raw logs.

Why package nerds care

xcbeautify is important in Apple-platform packaging because xcodebuild is unavoidable but noisy. It provides a small CLI layer that makes Xcode builds readable in terminal and CI logs without tying the workflow to Ruby.

Its role is also a good example of ecosystem succession: a Swift-native formatter increasingly replacing or supplementing xcpretty in places where Xcode's newer build and parallel-test output needed better handling.

Timeline

  • 2018: GitHub release history includes xcbeautify 0.3.6.
  • 2022: fastlane 2.201.0 and later document xcodebuild_formatter support and default to xcbeautify when installed.
  • 2023: 1.0.1 is published in the release stream.
  • 2024: 2.0.1 is published in the release stream.
  • 2026: 3.2.1 is released with fixes and additional CLI test coverage.

Related projects

  • xcbeautify is directly related to xcodebuild, Swift Package Manager, fastlane scan/gym/snapshot, and xcpretty.

approval gates

Human review metadata for risky commands

The local approval-gate seed includes 2 rules for xcbeautify. Covered entrypoints: xcbeautify. Severity labels: medium. Coverage: partial, reviewed 2026-05-21.

Example gated actions

  • Write formatted test or build reports.
  • Emit GitHub Actions annotations from build logs.

executables

Installed executables

CommandKindExposureNote
xcbeautifycliglobal 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.2.1
manager updated
local dataok
upstreamcurrent
latest detected3.2.1

https://github.com/cpisciotta/xcbeautify

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:xcbeautify
Version3.2.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/xcbeautify
Homepagehttps://github.com/cpisciotta/xcbeautify
Repositoryhttps://github.com/cpisciotta/xcbeautify
Upstream docshttps://github.com/cpisciotta/xcbeautify#readme
LicenseMIT
Source archivehttps://github.com/cpisciotta/xcbeautify/archive/refs/tags/3.2.1.tar.gz
Uses from macOSlibxml2
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 Namexcbeautify
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%

xcbeautify

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

xcbeautify

sudo port install xcbeautify
  • normalized package name match
  • Matched by: Xcbeautify
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/xcbeautify/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
  • approval-gate seed metadata
  • 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