dotenv
npm package · declared by 149 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 |
|---|---|---|
| express | 33 of 2,343 | 0.55 |
| cors | 16 of 2,343 | 0.50 |
| @google/genai | 8 of 2,343 | 0.45 |
| @anthropic-ai/sdk | 11 of 2,343 | 0.44 |
| axios | 26 of 2,343 | 0.42 |
| openai | 17 of 2,343 | 0.42 |
| jsonwebtoken | 9 of 2,343 | 0.39 |
| better-sqlite3 | 13 of 2,343 | 0.35 |
| node-fetch | 9 of 2,343 | 0.34 |
| @modelcontextprotocol/sdk | 22 of 2,343 | 0.33 |
| chokidar | 8 of 2,343 | 0.33 |
| zod | 36 of 2,343 | 0.32 |
| js-yaml | 9 of 2,343 | 0.28 |
| chalk | 11 of 2,343 | 0.28 |
| uuid | 11 of 2,343 | 0.28 |
| commander | 14 of 2,343 | 0.27 |
| ws | 10 of 2,343 | 0.23 |
| lucide-react | 16 of 2,343 | 0.19 |
| tailwind-merge | 10 of 2,343 | 0.13 |
| class-variance-authority | 8 of 2,343 | 0.12 |
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.