# Install aptos with Homebrew, winget

Layer 1 blockchain built to support fair access to decentralized assets for all. Version 9.5.0 via Homebrew; verified 2026-07-14. Also installable with winget: winget install --id AptosCore.aptos -e.

## Install

```sh
sudo av install brew:aptos
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install aptos
```

  Evidence: local Homebrew formula metadata

### Windows

- winget (92%):

```sh
winget install --id AptosCore.aptos -e
```

  Evidence: Windows Package Manager source index: AptosCore.aptos from https://cdn.winget.microsoft.com/cache/source.msix

## Package facts

- **Package key:** brew:aptos
- **Package manager:** Homebrew
- **Version:** 9.5.0
- **Source summary:** Layer 1 blockchain built to support fair access to decentralized assets for all
- **Homepage:** <https://aptosfoundation.org/>
- **Repository:** <https://github.com/aptos-labs/aptos-core>
- **Last updated:** 2026-07-14T11:43:38Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- aptos (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 9.5.0
## Project history and usage

Aptos CLI is the command-line front end for the Aptos blockchain toolchain. In package-manager terms it is the small executable that turns the much larger aptos-core monorepo into something developers can install, initialize, and use from a shell.

### Project history

The official aptos-core repository was created in February 2022 and describes Aptos as a layer 1 blockchain focused on broad blockchain use, better technology, and user experience. The Homebrew package exposes the `aptos` executable from that repository rather than a separate standalone CLI project.

Aptos documentation treats the CLI as the normal entry point for local developer work: users install it, initialize profiles, select network endpoints, generate or enter a private key, and then run account and Move-package workflows from the terminal.

### Adoption history

The CLI appears in Homebrew and winget package metadata, matching Aptos' cross-platform developer audience. The aptos-core repository is active and high-visibility, with thousands of stars and forks in the official GitHub API metadata.

Official release notes continue to mention CLI releases alongside node and framework changes, which is typical for chain toolchains where package users track both client compatibility and protocol cadence.

### How it is used

Typical use starts with `aptos init`, which writes a profile containing REST and faucet endpoints plus account key material. Named profiles let developers switch accounts and networks while reusing the same `aptos` binary for Move package publishing, account funding, and transaction workflows.

For package users, the important behavior is that local workspace configuration is discovered at `.aptos/config.yaml`, while a shared configuration can live at `~/.aptos/global_config.yaml`.

### Why package nerds care

Aptos CLI is a good example of a blockchain package where the executable, protocol implementation, SDK surface, and release engineering all live in one large monorepo. Packagers care about it because a CLI version is not just a convenience binary; it also encodes current Move tooling, network defaults, and compatibility expectations.

### Timeline

- 2022: The official aptos-core repository was created.
- 2022: Homebrew and other package metadata began distributing the `aptos` executable for developer workflows.
- 2026: Aptos node release notes still include explicit Aptos CLI release work, showing the CLI remains part of the main release train.

### Related projects

- Related official surfaces include aptos-core, the Aptos developer documentation, Move tooling, and Aptos network APIs.

### Sources

- <https://api.github.com/repos/aptos-labs/aptos-core>
- <https://api.github.com/repos/aptos-labs/aptos-core/releases>
- <https://aptos.dev/build/cli>
- <https://aptos.dev/build/cli/setup-cli>
- source_facts.package-manager


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## 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: .aptos/config.yaml, ~/.aptos/global_config.yaml

## Credential files

- Unix: .aptos/config.yaml, ~/.aptos/global_config.yaml
## Other Package-Manager Records

- winget - AptosCore.aptos: normalized package name match | Windows Package Manager source index: AptosCore.aptos from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/aptos.yml](https://github.com/mxcl/pkgdb/blob/main/combined/aptos.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph