axios
npm package · declared by 141 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 |
|---|---|---|
| form-data | 8 of 2,343 | 0.51 |
| uuid | 20 of 2,343 | 0.46 |
| jsonwebtoken | 10 of 2,343 | 0.43 |
| dotenv | 26 of 2,343 | 0.42 |
| dayjs | 9 of 2,343 | 0.41 |
| express | 20 of 2,343 | 0.40 |
| cors | 10 of 2,343 | 0.38 |
| react-hook-form | 8 of 2,343 | 0.36 |
| sharp | 12 of 2,343 | 0.35 |
| date-fns | 10 of 2,343 | 0.34 |
| react-router-dom | 10 of 2,343 | 0.29 |
| tailwindcss-animate | 8 of 2,343 | 0.28 |
| @radix-ui/react-slot | 11 of 2,343 | 0.28 |
| zustand | 9 of 2,343 | 0.27 |
| openai | 9 of 2,343 | 0.27 |
| next-themes | 9 of 2,343 | 0.25 |
| class-variance-authority | 14 of 2,343 | 0.25 |
| chalk | 9 of 2,343 | 0.25 |
| react-dom | 38 of 2,343 | 0.25 |
| react-markdown | 9 of 2,343 | 0.25 |
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.