commander
npm package · declared by 98 of 2,343 sampled repositories · graph computed 2026-08-24
Counted from the runtime dependencies public repositories declare — not the resolved tree. A transitive dependency is a consequence; a declared one is a choice. Development dependencies are excluded because they repeat across every project in a language regardless of what is being built.
Declared with
ranked by association, not by count| Declared with | Repositories | vs chance |
|---|---|---|
| chalk | 33 of 2,343 | 0.66 |
| ora | 21 of 2,343 | 0.66 |
| inquirer | 15 of 2,343 | 0.59 |
| @clack/prompts | 13 of 2,343 | 0.53 |
| fs-extra | 14 of 2,343 | 0.52 |
| open | 8 of 2,343 | 0.52 |
| fast-glob | 9 of 2,343 | 0.51 |
| picocolors | 9 of 2,343 | 0.51 |
| glob | 9 of 2,343 | 0.44 |
| chokidar | 9 of 2,343 | 0.39 |
| yaml | 12 of 2,343 | 0.37 |
| js-yaml | 11 of 2,343 | 0.36 |
| @modelcontextprotocol/sdk | 21 of 2,343 | 0.36 |
| ws | 14 of 2,343 | 0.34 |
| semver | 8 of 2,343 | 0.33 |
| undici | 8 of 2,343 | 0.31 |
| express | 12 of 2,343 | 0.29 |
| zod | 28 of 2,343 | 0.29 |
| dotenv | 14 of 2,343 | 0.27 |
| axios | 8 of 2,343 | 0.16 |
Every pair above is counted from the same evidence: repo manifest.
Used instead
candidates · shares a neighbourhood and refuses to co-occurNo alternative measured. A pair qualifies only if it shares a neighbourhood and then fails to appear together against an expectation that it would — and almost everything that shares a neighbourhood does appear together. That is the test working, not a gap in the data: similarity alone would list this tool’s closest neighbours as alternatives, and most of them are things it is used with.