# Install lacework-cli with Homebrew CLI for managing Lacework. Version 2.15.1 via Homebrew; verified 2026-07-26. ## Install ```sh sudo av install brew:lacework-cli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install lacework-cli ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:lacework-cli - **Package manager:** Homebrew - **Version:** 2.15.1 - **Source summary:** CLI for managing Lacework - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T13:40:58+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - lacework (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.15.1 ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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. ### Sources - - - - - - ## Security Notes No matching local secret-handling manifest was found for lacework-cli. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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: ~/.lacework.toml ## Credential files - Unix: ~/.lacework.toml ## Combined YAML source View the package source record on GitHub. [combined/lacework-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/lacework-cli.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph