@hookform/resolvers
npm package · declared by 77 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 |
|---|---|---|
| react-hook-form | 17 of 2,343 | 0.91 |
| @radix-ui/react-label | 11 of 2,343 | 0.71 |
| @radix-ui/react-dialog | 12 of 2,343 | 0.68 |
| @radix-ui/react-dropdown-menu | 9 of 2,343 | 0.63 |
| @radix-ui/react-slot | 12 of 2,343 | 0.62 |
| tailwindcss-animate | 9 of 2,343 | 0.61 |
| class-variance-authority | 13 of 2,343 | 0.56 |
| next-themes | 9 of 2,343 | 0.56 |
| tailwind-merge | 14 of 2,343 | 0.55 |
| clsx | 13 of 2,343 | 0.49 |
| lucide-react | 13 of 2,343 | 0.48 |
| zod | 17 of 2,343 | 0.48 |
| next | 13 of 2,343 | 0.43 |
| react-dom | 17 of 2,343 | 0.39 |
| react | 17 of 2,343 | 0.38 |
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.