riivault_

@vercel/analytics

npm package · declared by 76 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 withRepositoriesvs chance
@vercel/speed-insights11 of 2,3430.75
next34 of 2,3430.55
cmdk8 of 2,3430.53
@radix-ui/react-slot15 of 2,3430.51
clsx24 of 2,3430.50
@radix-ui/react-label9 of 2,3430.49
class-variance-authority18 of 2,3430.48
tailwind-merge20 of 2,3430.48
lucide-react23 of 2,3430.47
react-dom40 of 2,3430.46
next-themes11 of 2,3430.45
react40 of 2,3430.45
@radix-ui/react-dropdown-menu8 of 2,3430.44
@radix-ui/react-dialog9 of 2,3430.43
framer-motion9 of 2,3430.41
remark-gfm8 of 2,3430.37
react-markdown8 of 2,3430.36
zod15 of 2,3430.27

Every pair above is counted from the same evidence: repo manifest.

Used instead

candidates · shares a neighbourhood and refuses to co-occur

No 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.