# Install akamai with Homebrew

CLI toolkit for working with Akamai's APIs. Version 2.0.5 via Homebrew; verified 2026-07-26.

## Install

```sh
sudo av install brew:akamai
```

## Agent safety answer

akamai CLI controls Akamai edge configuration and account resources.

- **Credential access:** Reads Akamai credentials, edgerc files, account switches, and environment values.
- **Remote mutation:** Can change edge properties, purge caches, and mutate account configuration.
- **Publish/artifact risk:** Can publish edge delivery or security configuration.
- **Recommended control:** Gate property, purge, credential, and activation commands.
- **Agent-use guidance:** Allow read-only account inspection; require approval for activations, purges, and credential use.

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install akamai
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:akamai
- **Package manager:** Homebrew
- **Version:** 2.0.5
- **Source summary:** CLI toolkit for working with Akamai's APIs
- **Homepage:** <https://github.com/akamai/cli>
- **Repository:** <https://github.com/akamai/cli>
- **Last updated:** 2026-07-26T13:19:49+02:00
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- akamai (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Akamai CLI is Akamai's command-line framework for configuring Akamai platform products and APIs. The base `akamai` command is intentionally extensible: users install product-specific command packages, and those packages share conventions for authentication, command naming, and updates.

### Project history

The public GitHub repository was created in May 2017. The README describes a base CLI that can install ready-to-use product packages or serve as a framework for custom solutions written in Go, Python, or JavaScript.

The project adopted a package-oriented model inside the CLI itself. Built-in commands such as `install`, `uninstall`, `update`, `upgrade`, `search`, and `config` manage command packages under `$HOME/.akamai-cli`, while product packages use executable naming conventions such as `akamai-<command>`.

### Adoption history

Adoption follows Akamai's developer and operations audience. Official instructions cover release binaries, Homebrew, Docker images, and building from source, which made the CLI available both to local workstation users and CI/container users.

The README explicitly documents the Homebrew formula path for users who want package-manager updates, while non-Homebrew installs can use the CLI's own upgrade check introduced for v0.3.0 or later.

### How it is used

The central operational file is `~/.edgerc`, the standard EdgeGrid credential file. Akamai-branded packages use it by default, and commands can override the file and section with `--edgerc` and `--section`.

A common workflow is to install the base `akamai` command, install a product package such as Property Manager, then run product-specific commands with shared global flags such as `--accountkey`, `--edgerc`, and `--section`.

### Why package nerds care

Akamai CLI is interesting to package nerds because it is both a package and a package host. Homebrew installs the base binary, and the binary then manages its own Git-backed command packages in `$HOME/.akamai-cli`.

That layered model is common among vendor CLIs with broad API surfaces: keep the base command stable, then let product teams ship smaller command repositories without turning one formula into a giant monolith.

### Timeline

- 2017: Public `akamai/cli` repository created.
- v0.3.0 and later: README documents first-run automatic upgrade checks for non-Homebrew installs.
- 2026: Repository metadata still points users to Akamai developer CLI documentation.

### Related projects

- Akamai EdgeGrid: the authentication scheme and `.edgerc` credential format used by Akamai-branded CLI packages.
- akamai-docker: official Docker images that bundle the CLI and public packages.
- Akamai product CLI packages: GitHub repositories named with the `cli-` convention and installable through `akamai install`.

### Sources

- <https://api.github.com/repos/akamai/cli>
- <https://github.com/akamai/cli>
- <https://techdocs.akamai.com/developer/docs/about-clis>
- input source_facts.repo


## 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: ~/.akamai-cli/config

## Credential files

- Unix: ~/.edgerc

## Combined YAML source

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


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- curated agent safety answer