Automic VaultAutomic Vault

brew

Install lacework-cli with Homebrew

CLI for managing Lacework. Version 2.14.1 via Homebrew; verified 2026-06-23.

install

Additional install commands

macOS

Homebrewverified ยท 100%
brew install lacework-cli

local Homebrew formula metadata

overview

Package summary

CLI for managing Lacework

Commands and aliases

  • lacework

history

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.

security posture

No protected-tool coverage found yet

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.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

Installed executables

CommandKindExposureNote
laceworkcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version2.14.1
manager updated2026-06-23
local dataok
upstreamnot checked
latest detectednot detected

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

install metadata

Package metadata

Package keybrew:lacework-cli
Version2.14.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/lacework-cli
Homepagehttps://docs.lacework.com/cli
Repositoryhttps://github.com/lacework/go-sdk
Upstream docshttps://docs.lacework.net/cli
LicenseApache-2.0
Source archivehttps://github.com/lacework/go-sdk.git
Last updated2026-06-23T21:37:21Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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