🧹 Help us clean up duplicate (or unnecessary) libraries in Context7

[enesgules]

Hey everyone,

We need your help to clean up libraries in Context7.

While searching for a library, if you come across multiple instances of the same one, please report them under this issue. Include a screenshot or a short note about what you searched for and what you found, and we’ll clean up the duplicates.

Besides duplicates, you can also suggest libraries you think should be deleted—just let us know which ones and why.

Thanks in advance!

[mk11232]

A few questions about the quest:

Garbage Collection: Has the project considered automated removal based on usage metrics? Libraries unused/not-queried for 60+ days could be auto-removed since adding them back is trivial. This avoids manual bias and prevents "popularity contest" dynamics where newer libraries get unfairly targeted or someone just doesn't like an approach.

Duplicate Detection: I've tried submitting duplicates before and the system blocked me, so some detection exists. If not already implemented, hashing submissions and checking against existing github url would be straightforward and inexpensive to prevent duplicates upfront.

The "suggest libraries you think should be deleted" approach is a perfect example of the popularity contest issue - manual curation risks favoring established libraries over promising newcomers. Usage-based cleanup seems more objective and scalable.

[enesgules]

Yep we already check for duplicates, we will think about usage based cleanup thanks for the feedback!

[cobrabr]

https://context7.com/context7/docs_astral_sh-uv, https://context7.com/astral-sh/setup-uv and https://context7.com/llmstxt/docs_astral_sh-uv-llms.txt are duplicates of https://context7.com/astral-sh/uv

[kronaemmanuel]

https://context7.com/llmstxt/staging_bryntum-products-calendar-llms.txt is a duplicate and should be deleted, it's based on staging server

Actual library: https://context7.com/llmstxt/bryntum-products-calendar-llms.txt

[enesgules]

Hey @cobrabr are you sure if setup-uv is the same as uv?

[Tenelia]

This is somewhat an adjacent issue: I use TailwindCSS extensively, and the references often jump between v3 and v4 links. Even in v4 itself, the LLM pulls the wrong topic.
Today's example was perfect.
We wanted to test the TailwindCSS typography plugin, but the topic "typography plugin @plugin directive v4" pulling from "context7/tailwindcss" instead landed upon "Load Legacy Tailwind Plugin with @plugin directive".
There are clearly more relevant items in the entire library:
https://context7.com/context7/tailwindcss
But perhaps a library with 500k tokens bears a higher risk of misdirection? I can't even call this hallucination. It's clearly searched and landed on the wrong topic.

[enesakar]

hey Tenelia. The snippet about Legacy Tailwind Plugin exist in all docs resources including docs repo. I dont know how to filter it out. I hope AI agent would be smart enough to not to use a code flagged legacy.

https://github.com/tailwindlabs/tailwindcss.com/blob/main/src/docs/functions-and-directives.mdx#_snippet_11

[Tenelia]

It doesn't seem feasible because it still gets picked up in the wrong way. A misdirection causes the AI to thread the needle wrong, leading to a cascading series of missing imports, syntax issues, etc. Are you able to grep and remove sections? As things scale, you may need to have batch jobs setup for each lib.

[cobrabr]

Hey @cobrabr are you sure if setup-uv is the same as uv?

No, it's not, you're right. My bad, good catch.

[designgears]

You really need to add a voting system on the site, that way we downvote and flag stuff quickly, get enough votes and flags and it triggers a review.