# rotten

> figure out which branches in your git repository are rotten and haven't been merged into production in WAY too long.

Latest version **1.3.1** (published 2014-03-08) · 0 weekly downloads

## Install

```sh
npm install rotten
pnpm add rotten
yarn add rotten
bun add rotten
```

Provides the command `rotten`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.3.1 |
| Published | 2014-03-08 |
| First published | 2012-08-09 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Node | * |
| Dependencies | 3 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 36 |
| Author | David Trejo |
| Maintainers | dtrejo |

## Links

- npm: https://www.npmjs.com/package/rotten
- Repository: git@github.com:DTrejo/rotten
- Homepage: https://github.com/dtrejo/rotten
- Issues: https://github.com/DTrejo/rotten/issues
- npm.io page: https://npm.io/package/rotten

## Dependencies (3)

- [async](https://npm.io/package/async.md) ~0.1.22
- [colors](https://npm.io/package/colors.md) ~0.6.0-1
- [optimist](https://npm.io/package/optimist.md) ~0.3.4

## Recent versions

- 1.3.1 (latest) — 2014-03-08
- 1.3.0 — 2013-02-22
- 1.2.0 — 2012-12-12
- 1.1.2 — 2012-11-27
- 1.1.1 — 2012-11-27
- 1.1.0 — 2012-09-11
- 1.0.0 — 2012-09-11
- 0.1.2 — 2012-08-21
- 0.1.1 — 2012-08-09
- 0.1.0 — 2012-08-09
- 0.0.0 — 2012-08-09

## README

# Rotten — find empty git branches and unmerged ones with tons of code!

    $ npm -g install rotten

## It helps you discover
- Which remote branches are empty (all code is in master), also outputs a command to delete them all.
- Which remote branches still have lots of code that needs to be merged
- How long remote branches have been waiting to be merged.

## Why is this useful?
- discover which projects are languishing
- discover which engineers are unhappy that their code is not being reviewed/merged
- discover how effective your development process is

## How rotten am I really?
Try it out.

```sh
$ npm -g install rotten
$ cd my-big-git-repo
$ rotten
```

# Usage

```
Usage: rotten --repo /path-to-git-repo --prod master

Options:
  -r, --repo         the repo youd like to examine for rotting code                                        [default: "."]
  -p, --prod         the branch you have running in production                                             [default: "master"]
  --keep             don't run "harvested" checks (if you want to keep merged branches)                    [default: false]
  -c, --mostcommits  show branches with the most commits first (defaults to showing oldest commits first)  [default: false]
```

If you'd like to order by most commits waiting (instead of oldest commit waiting):

```sh
$ rotten --mostcommits
```


## Scoring?
`Your rotten score is #rotten:13/harvested:37`

Explanation:

- rotten: number of branches you need to merge into prod
- harvested: branches already in prod that need to be deleted.

---
_Source: https://npm.io/package/rotten · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._