# cloudsplaining を Homebrew でインストール

cloudsplaining のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:cloudsplaining
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install cloudsplaining
```

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:cloudsplaining
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.9.1
- **ソース概要:** AWS IAM Security Assessment tool
- **ホームページ:** <https://cloudsplaining.readthedocs.io/en/latest/>
- **リポジトリ:** <https://github.com/salesforce/cloudsplaining>
- **最終更新:** 2026-06-16T04:27:03Z
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- cloudsplaining (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 0.9.1
## プロジェクトの歴史と使われ方

Cloudsplaining is a Salesforce open source command-line tool for auditing AWS IAM policies and producing risk-prioritized least-privilege reports.

### プロジェクトの歴史

The project was created as a companion to Salesforce's Policy Sentry work: the README explains that Policy Sentry made least-privilege policy creation easier, but existing AWS accounts still had large backlogs of broad IAM policies that needed assessment.

Cloudsplaining's public release stream began in 2020, with the GitHub releases page marking version 0.0.2 as the open source release. The tool's core model has remained a CLI workflow that downloads AWS IAM account authorization details, scans them, and emits HTML plus JSON results.

### 採用の歴史

The upstream README documents installation through pip and Homebrew, including Salesforce's Homebrew tap, making it easy to put the scanner into Unix security and cloud-audit workflows.

Its adoption niche is AWS security engineering, penetration testing, and compliance review: it focuses on practical IAM risks such as data exfiltration, infrastructure modification, resource exposure, privilege escalation, and credentials exposure.

### 使われ方

Typical use starts with configured AWS credentials, `cloudsplaining download` to collect account authorization details, `cloudsplaining create-exclusions-file` to generate `exclusions.yml`, and `cloudsplaining scan` to generate reports.

The CLI can also scan a single IAM policy file, which makes it useful both for full-account audits and for reviewing individual policy documents during development.

### パッケージ好きにとっての重要性

Cloudsplaining is a good example of a cloud-security Python tool packaged for both pip and Homebrew: it turns a cloud API audit into a repeatable shell command that can live in developer laptops, CI jobs, and consulting toolkits.

### タイムライン

- 2020: Version 0.0.2 was published as the open source release on GitHub.
- 2020: Early releases added HTML report improvements, recursive scanning, trust-policy reporting, and automated Homebrew updates.
- 2020: The README documented both pip and Homebrew installation paths.

### Related projects

- Policy Sentry is the closest related Salesforce project and is cited in the README as the motivation for Cloudsplaining.
- Cloudsplaining also intersects with AWS IAM, AWS SecurityAudit-style permissions, and IAM privilege-escalation research such as Pathfinding.cloud.

### ソース

- <https://github.com/salesforce/cloudsplaining#readme>
- <https://cloudsplaining.readthedocs.io/en/latest/>
- <https://github.com/salesforce/cloudsplaining/releases>


## セキュリティノート

infrastructure mutation or orchestration signal.

- **Geiger リスク:** orange / 中
- infrastructure mutation or orchestration signal


## 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: ./exclusions.yml

## Credential files

- Unix: ~/.aws/credentials

## Combined YAML source

View the package source record on GitHub. [combined/cloudsplaining.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cloudsplaining.yml)


## ソース

- 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
