# Install nano with Homebrew

Free (GNU) replacement for the Pico text editor. Version 9.2 via Homebrew; verified 2026-07-31.

## Install

```sh
sudo av install brew:nano
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install nano
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:nano
- **Package manager:** Homebrew
- **Version:** 9.2
- **Source summary:** Free (GNU) replacement for the Pico text editor
- **Homepage:** <https://www.nano-editor.org/>
- **Last updated:** 2026-07-31T07:24:09Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- nano (alias)
- rnano (alias)

## Install behavior

- Bottle: not available

## Freshness

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

GNU nano is the small, friendly terminal text editor that began as a free replacement for Pico and became a default-ish editor across Unix-like systems.

### Project history

nano began in late 1999 when Chris Allegretta created TIP to provide a free software replacement for Pico, the editor bundled with the University of Washington's Pine mail client. The old nano FAQ says Debian's free-software standards kept Pine/Pico binaries out, leaving users who liked Pico's interface without a fully free package.

The name changed from TIP to nano on 2000-01-10 to avoid conflict with the existing Unix `tip` utility, and nano joined the GNU Project in February 2001. The project kept Pico's approachable modeless interface while adding capabilities that accumulated over time: regular-expression search, syntax highlighting, `.nanorc`, multiple buffers, UTF-8, undo/redo, line numbers, soft wrapping, file locking, and more.

### Adoption history

nano's adoption story is practical rather than flashy: it became the editor many distributions could ship when they wanted a Pico-like, GPL-compatible terminal editor for beginners and recovery shells. Its interface exposed common commands at the bottom of the screen, which made it friendlier than modal editors for quick edits to config files.

Homebrew's formula page consulted on 2026-07-01 listed nano 9.1 and 39,145 installs over the prior 365 days, far above the other packages in this batch. That Mac/Linuxbrew usage reflects its role as a familiar terminal editor even on systems that already ship another editor.

### How it is used

The manual describes the normal invocation as `nano [FILE]`, with optional line/column positioning, search-on-open, stdin editing via `nano -`, and configuration through nanorc files. Users edit directly because nano is modeless; control and meta key combinations handle save, exit, search, replace, cut, paste, help, and other commands.

Package nerds install nano for quick config edits, container images, remote shells, rescue environments, and scripts or docs that need an editor nearly anyone can operate. The restricted `rnano` binary is useful when an environment wants to limit file access and shell escapes.

### Why package nerds care

nano is significant because it solves the packaging and UX problem Pico could not: a small, libre, approachable terminal editor with few dependencies. It is the editor people install when 'just open the file and save it' matters more than an editor culture war.

### Timeline

- Late 1999: Chris Allegretta creates TIP as a free Pico replacement.
- 2000-01-10: TIP is renamed nano.
- 2001-02: nano becomes part of the GNU Project.
- 2007: nano switches to GPL-3.0-or-later licensing in the 2.0.7 era.
- 2026-06-23: nano homepage lists latest version 9.1.
- 2026-07-01: Homebrew Formulae page listed 39,145 installs over the prior 365 days.

### Related projects

- Pico
- Pine
- GNU Project
- ncurses

### Sources

- <https://formulae.brew.sh/formula/nano>
- <https://www.nano-editor.org/>
- <https://www.nano-editor.org/dist/latest/nano.html>
- <https://www.nano-editor.org/dist/v2.2/faq.html>
- <https://www.nano-editor.org/history.php>


## Security Notes

generalized runtime or code generation signal.

- **Geiger risk:** yellow / medium
- generalized runtime or code generation 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: /etc/nanorc, ~/.nanorc, $XDG_CONFIG_HOME/nano/nanorc, ~/.config/nano/nanorc

## Combined YAML source

View the package source record on GitHub. [combined/nano.yml](https://github.com/automic-vault/db/blob/main/combined/nano.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation