rich
pypi package · declared by 237 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 |
|---|---|---|
| typer | 66 of 2,343 | 0.57 |
| prompt-toolkit | 23 of 2,343 | 0.50 |
| python-frontmatter | 9 of 2,343 | 0.43 |
| click | 49 of 2,343 | 0.43 |
| questionary | 12 of 2,343 | 0.42 |
| textual | 13 of 2,343 | 0.41 |
| pyyaml | 79 of 2,343 | 0.40 |
| pydantic | 102 of 2,343 | 0.39 |
| pathspec | 12 of 2,343 | 0.38 |
| opentelemetry-sdk | 12 of 2,343 | 0.36 |
| psutil | 31 of 2,343 | 0.36 |
| docker | 8 of 2,343 | 0.34 |
| hydra-core | 8 of 2,343 | 0.34 |
| platformdirs | 11 of 2,343 | 0.34 |
| jinja2 | 32 of 2,343 | 0.33 |
| pydantic-settings | 37 of 2,343 | 0.33 |
| opentelemetry-api | 10 of 2,343 | 0.33 |
| filelock | 11 of 2,343 | 0.32 |
| watchdog | 12 of 2,343 | 0.32 |
| toml | 12 of 2,343 | 0.31 |
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.