# Install leetup with Homebrew

Command-line tool to solve Leetcode problems. Version 1.2.5 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:leetup
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install leetup
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:leetup
- **Package manager:** Homebrew
- **Version:** 1.2.5
- **Source summary:** Command-line tool to solve Leetcode problems
- **Homepage:** <https://github.com/dragfire/leetup>
- **Repository:** <https://github.com/dragfire/leetup>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- leetup (alias)

## Install behavior

- Bottle: not available

## Freshness

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

`leetup` is a Rust command-line tool for solving LeetCode problems from a terminal, with commands for login, picking problems, testing, submitting, listing, and injecting reusable code fragments.

### Project history

The README documents a terminal workflow centered on `leetup user -c`, `leetup pick`, `leetup test`, `leetup submit`, and `leetup list`. It also documents `~/.leetup/config.json` for language defaults, code injection, and pick hooks that run scripts before or after generated files are created.

The release stream visible on GitHub includes v1.1.0 on 2023-01-05, v1.2.0 on 2023-05-23 with cookie-login support, several September 2023 maintenance releases around test input and output printing, and v1.2.5 on 2024-03-24 with language-in-config support.

### Adoption history

The repository shows over a hundred stars and Homebrew packaging in the README. Its audience appears to be editor-and-terminal LeetCode users who want code generation and test submission without a browser-centered workflow.

### How it is used

Users install with Homebrew, Cargo, or release archives, authenticate by copying LeetCode cookie values, pick a problem in a target language, run local tests, submit a solution, and optionally configure reusable snippets or project-specific file movement hooks.

### Why package nerds care

Leetup is a compact example of the LeetCode CLI pattern in Rust: package-manager installation, authenticated web scraping/API use, local config under a dot directory, generated code markers, and hooks for reshaping output files into a user's preferred project layout.

### Timeline

- 2023-01-05: v1.1.0 was released.
- 2023-05-23: v1.2.0 added cookie-login support and improved result printing.
- 2023-09-04: v1.2.3 added stdin support for test data.
- 2023-09-09: v1.2.4 improved execution-result printing.
- 2024-03-24: v1.2.5 release notes mention language-in-config support.

### Related projects

- The README credits leetcode-tools/leetcode-cli as inspiration and also points Neovim users to leetup.nvim.

### Sources

- <https://github.com/dragfire/leetup>
- <https://github.com/dragfire/leetup/releases>


## 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: ~/.leetup/config.json

## Combined YAML source

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