Automic VaultAutomic Vault

brew

austin mit Homebrew, apt, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für austin in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install austin

local Homebrew formula metadata

Linux

Debian aptverifiziert · 92%
sudo apt install austin

Debian stable package indexes · austin · Quelle: deb.debian.org

Windows

Scoopverifiziert · 92%
scoop install main/austin

Scoop official bucket manifest trees · bucket/austin.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%
winget install --id P403n1x87.austin -e

Windows Package Manager source index · P403n1x87.austin · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Python frame stack sampler for CPython

Befehle und Aliase

  • austin

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
austincliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version4.0.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv4.0.0

https://github.com/P403n1x87/austin

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:austin
Version4.0.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/austin
Homepagehttps://github.com/P403n1x87/austin
Repositoryhttps://github.com/P403n1x87/austin
Upstream-Dokumentationhttps://github.com/P403n1x87/austin#readme
LizenzGPL-3.0-or-later
Quellarchivhttps://github.com/P403n1x87/austin/archive/refs/tags/v4.0.0.tar.gz
Build-Abhängigkeitenautoconf, automake
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

austin 3.7.0-4

Frame stack sampler for CPython

https://github.com/P403n1x87/austin

sudo apt install austin
  • Section: devel
  • Architecture: amd64
  • 6 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Austin
Debian stable package indexes · deb.debian.org · Debian stable package indexes: austin from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt95%

austin 1.0.1-2

Frame stack sampler for CPython

https://github.com/P403n1x87/austin

sudo apt install austin
  • Section: universe/devel
  • Architecture: amd64
  • 1 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Austin
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: austin from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
Scoop95%

main/austin

scoop install main/austin
  • normalized package name match
  • Abgeglichen nach: Austin
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/austin.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
winget95%

P403n1x87.austin

winget install --id P403n1x87.austin -e
  • normalized package name match
  • Abgeglichen nach: Austin
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: P403n1x87.austin from https://cdn.winget.microsoft.com/cache/source.msix

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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