# Install austin with Homebrew, apt, scoop, winget Python frame stack sampler for CPython. Version 4.0.0 via Homebrew; verified from local package data. Also installable with debian: sudo apt install austin. ## Install ```sh sudo av install brew:austin ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install austin ``` Evidence: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install austin ``` Evidence: Debian stable package indexes: austin from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ### Windows - Scoop (92%): ```sh scoop install main/austin ``` Evidence: Scoop official bucket manifest trees: bucket/austin.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id P403n1x87.austin -e ``` Evidence: Windows Package Manager source index: P403n1x87.austin from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:austin - **Package manager:** Homebrew - **Version:** 4.0.0 - **Source summary:** Python frame stack sampler for CPython - **Homepage:** - **Repository:** - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - austin (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 4.0.0 ## Project history and usage Austin is a CPython frame-stack sampler written in C. It sits in the package-manager sweet spot for profilers: a small native command, installable from several ecosystems, that can attach to a Python process without instrumentation and emit data for flame graphs, Speedscope, and other tooling. ### Project history The public GitHub repository was created in September 2018 and describes Austin as a pure-C sampler that reads the CPython interpreter's memory to recover executing frames and threads. Its own README emphasizes zero instrumentation, low overhead, wall-time and memory profiling, and multiprocess support. Austin has tracked CPython internals over time. Recent official releases added CPython 3.12, 3.13, and 3.14 support, dropped older interpreter support, improved container and interpreter detection, and moved the default binary output format to MOJO in the 4.0.0 series. ### Adoption history Austin became more than a GitHub-only tool early in its life: the README notes acceptance into Debian repositories on March 30, 2019, and documents installation through PyPI, Snap, Debian/apt, Homebrew, Chocolatey, Scoop, and Conda Forge. Homebrew's formula currently packages Austin 4.0.0 from the upstream GitHub release tarball. The repository metadata shows thousands of GitHub stars and ongoing releases, while Homebrew analytics in the formula API show modest but real package-manager use. For a native Python profiler, that breadth of packaging is part of the story: users can install it as a system command instead of treating it as a Python library dependency. ### How it is used Austin is typically used by running `austin` around or against a Python workload, then feeding its collapsed-stack or binary output into visualization tools. The README explicitly calls out use with the Austin VS Code extension, Brendan Gregg's FlameGraph tools, and Speedscope conversion through the related Austin Python tooling. Its value is operational: no source-code instrumentation, low tracee impact, support for memory mode, and enough portability to cover Linux, macOS, and Windows packaging paths. ### Why package nerds care Package nerds care about Austin because it is a native executable wrapped by language and OS package managers at once. It is distributed as `austin-dist` on PyPI, as a Homebrew formula, as OS packages, and as release binaries, while still depending on CPython implementation details that require active maintenance. It is also a good example of a CLI whose package identity is not quite the same as its library ecosystem identity: the Homebrew formula is `austin`, the PyPI install is `austin-dist`, and the output is meant to be composed with classic Unix-style profiler visualization tools. ### Timeline - 2018: Public GitHub repository created. - 2019: Austin accepted into the official Debian repositories. - 2023: Austin 3.6.0 added CPython 3.12 support and dropped Python 2 and older CPython 3 releases. - 2024: Austin 3.7.0 added CPython 3.13 support and improved container support. - 2025: Austin 4.0.0 added CPython 3.14 support and made MOJO binary output the default. ### Related projects - Austin commonly appears alongside FlameGraph, Speedscope, the Austin VS Code extension, and the `austin-python` tooling used for conversion and higher-level profiler workflows. ### Sources - - - - - source_facts.package-manager ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Other Package-Manager Records - Debian apt - austin - 3.7.0-4: normalized package name match | Debian stable package indexes: austin from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Frame stack sampler for CPython | https://github.com/P403n1x87/austin - Ubuntu apt - austin - 1.0.1-2: normalized package name match | Ubuntu 24.04 LTS package indexes: austin from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Frame stack sampler for CPython | https://github.com/P403n1x87/austin - Scoop - main/austin: normalized package name match | Scoop official bucket manifest trees: bucket/austin.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget - P403n1x87.austin: normalized package name match | Windows Package Manager source index: P403n1x87.austin from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/austin.yml](https://github.com/mxcl/pkgdb/blob/main/combined/austin.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