Automic VaultAutomic Vault

brew

lacework-cli mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install lacework-cli

local Homebrew formula metadata

Überblick

Paketzusammenfassung

CLI for managing Lacework

Verlauf

Projektgeschichte und Nutzung

Lacework CLI is the command-line interface for managing the Lacework cloud security platform. It is shipped from the Lacework Go SDK repository alongside Go client libraries, config helpers, an updater, and API examples.

The tool is service-specific, but it has package-manager significance because cloud-security teams use it for compliance reports, cloud integrations, vulnerability scans, API access, and automation around Lacework accounts.

Projektgeschichte

The go-sdk repository states that it provides tools, libraries, documentation, samples, and guides for interacting with the Lacework platform. The CLI sits under that repository as the user-facing command-line layer.

The CLI README documents cross-platform installation through shell scripts, PowerShell, Homebrew, Chocolatey, and Azure Cloud Shell. Development examples in the same README show a 0.1.1-dev build string from April 2020, placing the CLI's public development era in the early Lacework automation period.

Adoptionsgeschichte

Adoption follows Lacework platform usage rather than a general open source community. The CLI stores account, API key, and secret configuration in `$HOME/.lacework.toml`, supports profiles and environment variables, and exposes commands that match Lacework operational areas.

The release feed and release notes show continued packaging of signed binaries and Docker images, including v2.x release artifacts for macOS, Linux, Windows, and container workflows.

Wie es verwendet wird

Users run `lacework configure` to create a profile, then use commands such as `lacework cloud-account list`, `lacework events list`, `lacework vulnerability container scan`, and `lacework api get /schemas`.

For automation, the CLI can read `LW_` environment variables, switch profiles, disable interactivity, emit JSON, and run in cloud shell or CI contexts where API keys are provided by the environment.

Warum Paket-Nerds sich dafür interessieren

The package is a representative vendor CLI: the local binary is small, but it encodes a cloud platform's API, credential conventions, profile model, and release cadence.

Its presence in Homebrew also shows how security platforms meet users where operational scripts live, with packaged binaries, checksums, Docker images, and shell-install fallbacks.

Zeitleiste

  • 2020: CLI development examples showed a 0.1.1-dev build string and Makefile install flow.
  • 2020: The repository copyright and SDK documentation identified Lacework Inc. as steward of the Go SDK and CLI code.
  • 2020s: The CLI documented Homebrew, Chocolatey, Bash, PowerShell, Azure Cloud Shell, and Docker installation paths.
  • 2026: v2.14.1 release artifacts included signed platform archives and a Docker image.

Related projects

  • The Lacework Go API client, lwconfig, lwupdater, and lwdomain packages live in the same repository and support the CLI's platform interaction model.
  • The Lacework Terraform provider and other Lacework SDKs are adjacent automation surfaces for the same cloud-security platform.
  • Docker images for `lacework/lacework-cli` provide an alternative packaging path for CI and ephemeral automation.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für lacework-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

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
~/.lacework.toml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.lacework.toml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
laceworkcliglobales 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-25
Manager-Version2.15.1
Manager aktualisiert2026-07-23
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/lacework/go-sdk

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:lacework-cli
Version2.15.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/lacework-cli
Homepagehttps://docs.lacework.com/cli
Repositoryhttps://github.com/lacework/go-sdk
Upstream-Dokumentationhttps://docs.lacework.net/cli
LizenzApache-2.0
Quellarchivhttps://github.com/lacework/go-sdk.git
Zuletzt aktualisiert2026-07-23T00:59:53Z
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 Namelacework-cli
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 configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment