pkg.soopen package index

brew / rank 2210

Install cloud-nuke with Homebrew, Nix, scoop, winget

CLI tool to nuke (delete) cloud resources. Version 0.52.0 via Homebrew; verified 2026-07-27. Also installable with nix: nix profile install nixpkgs#cloud-nuke.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install cloud-nuke

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#cloud-nuke

nixpkgs package indexes · pkgs/by-name/cl/cloud-nuke/package.nix · source: api.github.com

Windows

Scoopverified · 92%
scoop install main/cloud-nuke

Scoop official bucket manifest trees · bucket/cloud-nuke.json · source: api.github.com

Windows Package Managerverified · 92%
winget install --id Gruntwork.cloud-nuke -e

Windows Package Manager source index · Gruntwork.cloud-nuke · source: cdn.winget.microsoft.com

overview

Package summary

CLI tool to nuke (delete) cloud resources

Commands and aliases

  • cloud-nuke

history

Project history and usage

cloud-nuke is Gruntwork's destructive cleanup CLI for deleting cloud resources, mainly used around test accounts, ephemeral infrastructure, and default AWS resource cleanup. Its history is source-backed enough to treat it as a real package-manager tool rather than just a GitHub utility.

Project history

The gruntwork-io/cloud-nuke repository was created in 2017 and is maintained by Gruntwork. The README frames the tool as a way to remove leftover resources, clean test accounts, and delete defaults such as default VPCs and permissive security group rules.

The tool evolved from AWS-focused cleanup into a CLI with inspect, dry-run, filtering, config-file, and GCP commands. The README also documents telemetry added as of v0.29.0, showing a maintained packaged CLI rather than a one-off script.

Adoption history

Official installation docs point users to GitHub release binaries and explicitly list Homebrew for macOS and Linux plus winget for Windows. The input package-manager facts also record Nix, Scoop, and winget identifiers, so adoption is package-manager centric even though upstream cautions that package-manager builds may lag releases.

The CLI is significant in infrastructure shops because it turns account cleanup into a repeatable command with filters, dry-run, region selection, resource-type selection, and config-driven targeting.

How it is used

Common use is `cloud-nuke aws` for deletion, `cloud-nuke inspect-aws` for inspection, `cloud-nuke defaults-aws` for default VPC and security group cleanup, and `cloud-nuke gcp` for GCP deletion. The official docs emphasize dry-run and filtering because the default delete path is intentionally dangerous.

Credentials come from standard AWS CLI credential mechanisms for AWS usage, and the tool accepts command flags plus an optional user-supplied config file path for granular filtering.

Why package nerds care

cloud-nuke is a good example of a high-blast-radius CLI where package freshness, binary provenance, and default behavior matter. Upstream warns users to compare package-manager versions with GitHub releases.

For Homebrew and cross-platform package indexes, it is notable because it packages operational cloud deletion behavior as a one-command executable rather than a library.

Timeline

  • 2017: gruntwork-io/cloud-nuke GitHub repository metadata was created.
  • v0.29.0: Upstream README records the addition of telemetry.
  • Current docs: Official install instructions list release binaries, Homebrew, and winget.

Related projects

  • Gruntwork's broader infrastructure tooling ecosystem is the upstream context for cloud-nuke.
  • AWS CLI credential files and GCP project credentials are operational dependencies for the supported cloud providers.
  • Cloud clean-up and account janitor tools occupy the same niche, but cloud-nuke is the package in this batch with explicit package-manager distribution.

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:cloud

Install behavior

  • No Homebrew bottle metadata was recorded.

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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.aws/credentials~/.aws/config
Windows
%UserProfile%\.aws\credentials%UserProfile%\.aws\config

executables

Installed executables

CommandKindExposureNote
cloud-nukeexecutableindexed executableDiscovered from the local executable index.

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-08-03
manager version0.52.0
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:cloud-nuke
Version0.52.0
Package managerHomebrew
Homepagehttps://gruntwork.io/
Repositoryhttps://github.com/gruntwork-io/cloud-nuke
Last updated2026-07-27T22:04:01+02:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

cloud-nuke

nix profile install nixpkgs#cloud-nuke
  • normalized package name match
  • Matched by: Cloud Nuke
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/cl/cloud-nuke/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

main/cloud-nuke

scoop install main/cloud-nuke
  • normalized package name match
  • Matched by: Cloud Nuke
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/cloud-nuke.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
winget95%

Gruntwork.cloud-nuke

winget install --id Gruntwork.cloud-nuke -e
  • normalized package name match
  • Matched by: Cloud Nuke
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Gruntwork.cloud-nuke from https://cdn.winget.microsoft.com/cache/source.msix

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation