riivault_

react-markdown

npm package · declared by 117 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
remark-gfm42 of 2,3430.84
rehype-raw15 of 2,3430.71
rehype-sanitize12 of 2,3430.70
rehype-katex13 of 2,3430.64
remark-math13 of 2,3430.63
rehype-highlight8 of 2,3430.61
fuse.js8 of 2,3430.54
lucide-react35 of 2,3430.54
katex11 of 2,3430.51
react-dom54 of 2,3430.49
react-router-dom15 of 2,3430.49
react54 of 2,3430.47
react-hook-form8 of 2,3430.44
@radix-ui/react-slot14 of 2,3430.43
clsx23 of 2,3430.41
zustand11 of 2,3430.40
@radix-ui/react-label8 of 2,3430.40
@radix-ui/react-dialog10 of 2,3430.39
next26 of 2,3430.38
framer-motion10 of 2,3430.37

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.