# Install stormy with Homebrew

Minimal, customizable and neofetch-like weather CLI based on rainy. Version 0.3.3 via Homebrew; verified 2026-07-26.

## Install

```sh
sudo av install brew:stormy
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install stormy
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:stormy
- **Package manager:** Homebrew
- **Version:** 0.3.3
- **Source summary:** Minimal, customizable and neofetch-like weather CLI based on rainy
- **Homepage:** <https://github.com/ashish0kumar/stormy>
- **Repository:** <https://github.com/ashish0kumar/stormy>
- **Last updated:** 2026-07-26T04:03:47+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- stormy (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.3.3
## Project history and usage

stormy is a small Go weather CLI with a neofetch-like terminal display. It is a package-manager-friendly terminal toy/productivity utility: install it, run `stormy`, and get current weather with ASCII art.

### Project history

The README says stormy was inspired by rainy and built in Go because the author liked the idea of a Neofetch-style weather CLI. The repository marks the project as 2025-present and documents a local configuration file created on first run.

### Adoption history

The supplied Homebrew metadata shows stormy as a Brew formula. Upstream also documents `go install github.com/ashish0kumar/stormy@latest`, so its initial adoption path is split between Go's native installer and package-manager distribution.

### How it is used

The README documents OpenMeteo as the default provider with no API key required and OpenWeatherMap as an optional provider. Users can configure city, units, colors, compact display, and an optional OpenWeatherMap API key in `stormy.toml`.

### Why package nerds care

stormy matters mostly as a modern terminal-culture package: it combines Go single-binary distribution, weather APIs, XDG-style config on Unix, Windows config support, and the neofetch habit of making useful information visually pleasant in a shell.

### Timeline

- 2025: README copyright marks stormy as 2025-present.
- 2025: README documents Go installation and local config creation on first run.
- Current: Homebrew metadata packages the `stormy` executable.

### Related projects

- The README credits rainy for the idea, structure, and design, OpenWeatherMap and Open-Meteo for weather data, and wttr.in for ASCII weather icons.

### Sources

- <https://github.com/ashish0kumar/stormy#readme>
- <https://raw.githubusercontent.com/ashish0kumar/stormy/main/README.md>
- input.source_facts.package-manager


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## 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: ~/.config/stormy/stormy.toml
- Windows: %APPDATA%\stormy\stormy.toml

## Credential files

- Unix: ~/.config/stormy/stormy.toml
- Windows: %APPDATA%\stormy\stormy.toml

## Combined YAML source

View the package source record on GitHub. [combined/stormy.yml](https://github.com/mxcl/pkgdb/blob/main/combined/stormy.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