# asyncapi mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:asyncapi
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install asyncapi
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#asyncapi
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/as/asyncapi/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:asyncapi
- **Paketmanager:** Homebrew
- **Paketmanager-Seite:** <https://formulae.brew.sh/formula/asyncapi>
- **Version:** 6.0.2
- **Quellzusammenfassung:** All in one CLI for all AsyncAPI tools
- **Homepage:** <https://www.asyncapi.com/tools/cli>
- **Repository:** <https://github.com/asyncapi/cli>
- **Upstream-Dokumentation:** <https://www.asyncapi.com/docs/tools/cli>
- **Lizenz:** Apache-2.0
- **Quellarchiv:** <https://registry.npmjs.org/@asyncapi/cli/-/cli-6.0.2.tgz>
- **Zuletzt aktualisiert:** 2026-06-15T10:20:10-04:00
- **Generiert:** 2026-07-08T18:08:21+00:00

## Executables

- asyncapi (cli)
- asyncapi (Alias)

## Abhängigkeiten

- node

## Installationsverhalten

- Post-install-Hook: nicht definiert
- Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Version und Aktualität

- Seite generiert: 2026-07-08
- Manager-Version: 6.0.2
- Manager aktualisiert: 2026-06-15
- lokale Daten: OK
- Upstream-Repository: https://www.asyncapi.com/tools/cli
- Info: Release/tag comparison is only available for GitHub repositories.
## Projektgeschichte und Nutzung

AsyncAPI CLI is the command-line front end for working with AsyncAPI documents: validating, bundling, converting, formatting, diffing, generating clients/models/templates, launching previews and Studio, and managing document contexts. It is the package-manager face of the wider AsyncAPI Initiative.

### Projektgeschichte

The CLI repository began in 2021 with an explicit design phase and grew into an oclif-based Node.js command suite. Its README describes it as a CLI for AsyncAPI files and points contributors to generated usage docs, architecture docs, and command patterns such as `verb + noun` and `namespace + noun + verb`.

The 5.x and 6.x lines show the project consolidating around document operations and generator integration. Version 6.0.0 removed Postman-to-AsyncAPI conversion support because the dependency chain had become unmaintained and difficult to support, which is a good example of the CLI being maintained as a practical tool rather than only an aggregation point.

### Adoptionsgeschichte

AsyncAPI CLI is shipped through npm, Homebrew, Docker, macOS pkg files, Windows installers, Chocolatey, Debian packages, and other package channels documented by the project. The supplied Homebrew and Nix package metadata shows it has crossed from the JavaScript ecosystem into system package-manager catalogs.

Its adoption follows the growth of AsyncAPI as a specification for event-driven and asynchronous APIs: teams that already keep OpenAPI-like documents in repositories can add the CLI to CI, local validation, code-generation, documentation-preview, and schema-maintenance workflows.

### Wie es verwendet wird

Common package-manager usage is `asyncapi validate`, `asyncapi bundle`, `asyncapi diff`, `asyncapi generate`, `asyncapi start preview`, and `asyncapi start studio`. The CLI also has context commands for giving short names to AsyncAPI document paths and auth commands for resolving protected remote references.

### Warum Paket-Nerds sich dafür interessieren

AsyncAPI CLI is interesting because it is both a Node package and a cross-platform native-feeling CLI artifact. Package maintainers have to care about npm global installs, generated oclif command docs, shell completion, Docker images, OS installers, Homebrew bottles, and the fast-moving AsyncAPI toolchain behind the single `asyncapi` executable.

### Zeitleiste

- 2021: Initial CLI repository commits and design notes.
- 2026: v6.0.0 removed Postman conversion support after dependency-maintenance issues.
- 2026: v6.0.2 patched request-body validation behavior.

### Related projects

- Related AsyncAPI projects include the AsyncAPI specification, generator, converter-js, Studio/preview tooling, templates, parser tooling, and the broader event-driven API documentation ecosystem.

### Quellen

- Official git metadata from https://github.com/asyncapi/cli.git
- <https://github.com/asyncapi/cli#readme>
- <https://github.com/asyncapi/cli/blob/master/docs/installation.md>
- <https://github.com/asyncapi/cli/blob/master/docs/usage.md>
- <https://github.com/asyncapi/cli/releases.atom>


## Sicherheitshinweise

broad file, network, media, or database tool signal.

- **Geiger-Risiko:** blue / mittel
- broad file, network, media, or database tool signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .asyncapi-cli, ~/.asyncapi-cli
## Details aus der Quelldatenbank

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** asyncapi
- **Version Scheme:** 1
- **Revision:** 0
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** stable

## Andere Paketmanager-Einträge

- Nix - asyncapi: normalized package name match | nixpkgs package indexes: pkgs/by-name/as/asyncapi/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Verwandte Links

- [Secret-risk packages](https://www.automicvault.com/de/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals.
- [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/de/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://www.automicvault.com/de/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [node](https://www.automicvault.com/de/pkg/brew/node/) - Runtime dependency declared by Homebrew.
- [algolia](https://www.automicvault.com/de/pkg/brew/algolia/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [apfel](https://www.automicvault.com/de/pkg/brew/apfel/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [api-linter](https://www.automicvault.com/de/pkg/brew/api-linter/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [apibuilder-cli](https://www.automicvault.com/de/pkg/brew/apibuilder-cli/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [apigeecli](https://www.automicvault.com/de/pkg/brew/apigeecli/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [atac](https://www.automicvault.com/de/pkg/brew/atac/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [autocode](https://www.automicvault.com/de/pkg/brew/autocode/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [autorest](https://www.automicvault.com/de/pkg/brew/autorest/) - Shares av.db curated category or tags: api, cli, developer-tools.
- [redocly-cli](https://www.automicvault.com/de/pkg/brew/redocly-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: all, api, cli, developer, developer-tools.
- [spectral-cli](https://www.automicvault.com/de/pkg/brew/spectral-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: api, asyncapi, cli, developer, developer-tools.

## Combined YAML source

View the package source record on GitHub. [combined/asyncapi.yml](https://github.com/automic-vault/db/blob/main/combined/asyncapi.yml)


## Quellen

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
