asyncapi/cli has 277 GitHub stars and 390 forks. GitHot measured 0 stars in 24 hours, 0 in 7 days, and +1 in 15 days. Last checked 2026-11-18 01:59 UTC. Last push 2026-11-07.
Measured star growth
- in 24h
- 0
- in 7 days
- 0
- in 15 days
- +1
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!
Developer ToolsREADME.md
OriginalCLI to work with your AsyncAPI files. Currently under development, we are working to bring more features.
Table of contents
Installation
Learn how to install the AsyncAPI CLI by following the instructions in the installation guide.
Usage
The usage guide provides information about different ways to use the CLI.
Architecture
The architecture guide provides information about the architecture. The bundler library lives in this repo at packages/bundler.
Debugging & Testing
The debugging & testing guide provides step-by-step instructions for debugging CLI commands, API endpoints, and services, along with comprehensive testing guidelines.
Github Action
The AsyncAPI CLI can be used as a GitHub Action. You can find more information in the GitHub Action guide.
Contributing
Read CONTRIBUTING guide.
Set up development environment
Read DEVELOPMENT.md file for development setup.
Additional steps:
- Run
npm run testto make sure everything is properly set up - Run
npm run buildand thenbin/runto try new CLI locally
This repository is an npm-workspaces + Turbo monorepo. The root package is
@asyncapi/cli(workspaces include"."so Changesets still versions it like today).@asyncapi/optimizerlives inpackages/optimizer/and@asyncapi/difflives inpackages/diff/. Both are published separately to npm. Usenpm run optimizer:build/npm run optimizer:testandnpm run diff:build/npm run diff:testto work on those packages. See their specs: optimizer, diff.
The UX developed for the CLI should comply with the Command Line Interface Guideline
Command Structure and Patterns
We are following verb + noun and namespace + noun + [verb] pattern for making our commands and arguments. For example asyncapi validate <spec-file-path> and asyncapi config context add <context-name> <spec-file-path>.
Contributors
Thanks go to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
