Automic VaultAutomic Vault

brew

akamai mit Homebrew installieren

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

Agent-Sicherheit

Antwort zur Agent-Sicherheit

akamai CLI controls Akamai edge configuration and account resources.

Credential-Zugriff

Reads Akamai credentials, edgerc files, account switches, and environment values.

Änderungen an Remote-Zustand

Can change edge properties, purge caches, and mutate account configuration.

Publish-/Artefakt-Risiko

Can publish edge delivery or security configuration.

Empfohlene Kontrolle

Gate property, purge, credential, and activation commands.

Hinweise für Agent-Nutzung

Allow read-only account inspection; require approval for activations, purges, and credential use.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install akamai

local Homebrew formula metadata

Überblick

Paketzusammenfassung

CLI toolkit for working with Akamai's APIs

Befehle und Aliase

  • akamai

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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

Adoptionsgeschichte

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.

Wie es verwendet wird

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

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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

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

local files

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

Config paths the tool may read or write during local use.

Unix
~/.akamai-cli/config

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.edgerc

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
akamaicliglobales 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-Version2.0.4
Manager aktualisiert2026-06-09
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.0.4

https://github.com/akamai/cli

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:akamai
Version2.0.4
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/akamai
Homepagehttps://github.com/akamai/cli
Repositoryhttps://github.com/akamai/cli
Upstream-Dokumentationhttps://github.com/akamai/cli
LizenzApache-2.0
Quellarchivhttps://github.com/akamai/cli/archive/refs/tags/v2.0.4.tar.gz
Zuletzt aktualisiert2026-06-09T09:09:23Z
Pulseupdated
Build-Abhängigkeitengo
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 Nameakamai
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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 agent safety answer
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment