You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🧹 Help us clean up duplicate (or unnecessary) libraries in Context7 #339
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.
changed the title [-]Help us clean up duplicate (or unnecessary) libraries in Context7[/-][+]🧹 Help us clean up duplicate (or unnecessary) libraries in Context7[/+]on Jun 27, 2025
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.
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.
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.
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.
Both entries appear to represent the Nuxt 4 documentation. The first entry indexes the official https://nuxt.com/docs/4.x/ documentation and currently contains 270 pages and 1,451 snippets.
The second entry points to https://nuxt.com/docs/v4/, which currently returns a 404. Its configured input URL also appears to be an unrelated Nuxt module page (https://nuxt.com/modules/auto-animate). It contains only one snippet and has a benchmark score of 0.
I suggest removing or redirecting /websites/nuxt_v4 to /websites/nuxt_4_x.
Hi, if there is a one source where it contains all the info that is found in others and even more, we redirect other entries to it.
@enesgules Thanks for redirecting Deno Docs. How is the last update computed for redirects? Shouldn't it be the same as the redirect target?
Hi, this date shows the number when the redirected library was last parsed. But I get how it can be confusing. Maybe we can stop displaying some of these values here.
Both entries appear to represent the Nuxt 4 documentation. The first entry indexes the official https://nuxt.com/docs/4.x/ documentation and currently contains 270 pages and 1,451 snippets.
The second entry points to https://nuxt.com/docs/v4/, which currently returns a 404. Its configured input URL also appears to be an unrelated Nuxt module page (https://nuxt.com/modules/auto-animate). It contains only one snippet and has a benchmark score of 0.
I suggest removing or redirecting /websites/nuxt_v4 to /websites/nuxt_4_x.
Advanced https://paymenku.com/merchant/api-docs
Only pages starting with this URL will be crawled. Useful for limiting the crawler to a specific section of the website.
Submit
Website score 1 below threshold 9
If you think this is a mistake, please open an issue.
Duplicate: walkerOS is listed twice, /elbwalker/walkeros (repo, claimed by me as maintainer, now with context7.json) and /websites/walkeros_io (the docs site, generated from the same repo). Searching "walkerOS" returns both. Please remove /websites/walkeros_io and keep the repo entry. Thanks.
Advanced paymenku.com/merchant/api-docs Only pages starting with this URL will be crawled. Useful for limiting the crawler to a specific section of the website.
Submit Website score 1 below threshold 9 If you think this is a mistake, please open an issue.
Duplicate: walkerOS is listed twice, /elbwalker/walkeros (repo, claimed by me as maintainer, now with context7.json) and /websites/walkeros_io (the docs site, generated from the same repo). Searching "walkerOS" returns both. Please remove /websites/walkeros_io and keep the repo entry. Thanks.
I redirected the website to the repo and verified the repo while at it!
Activity
[-]Help us clean up duplicate (or unnecessary) libraries in Context7[/-][+]🧹 Help us clean up duplicate (or unnecessary) libraries in Context7[/+]mk11232 commentedon Jun 27, 2025
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 commentedon Jul 4, 2025
Yep we already check for duplicates, we will think about usage based cleanup thanks for the feedback!
cobrabr commentedon Jul 13, 2025
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 commentedon Jul 14, 2025
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 commentedon Jul 22, 2025
Hey @cobrabr are you sure if setup-uv is the same as uv?
Tenelia commentedon Jul 22, 2025
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 commentedon Jul 22, 2025
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 commentedon Jul 22, 2025
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 commentedon Jul 23, 2025
No, it's not, you're right. My bad, good catch.
designgears commentedon Aug 4, 2025
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.
75 remaining items
lurui1997 commentedon Jul 22, 2026
Search term:
nuxtI found what appears to be a duplicate or misconfigured Nuxt 4 entry:
Both entries appear to represent the Nuxt 4 documentation. The first entry indexes the official
https://nuxt.com/docs/4.x/documentation and currently contains 270 pages and 1,451 snippets.The second entry points to
https://nuxt.com/docs/v4/, which currently returns a 404. Its configured input URL also appears to be an unrelated Nuxt module page (https://nuxt.com/modules/auto-animate). It contains only one snippet and has a benchmark score of 0.I suggest removing or redirecting
/websites/nuxt_v4to/websites/nuxt_4_x.z2vvqx commentedon Jul 23, 2026
context7.com/websites/jd_papermc_io_velocity_3_5_0 is an outdated version of context7.com/websites/jd_papermc_io_velocity_4_1_0
enesgules commentedon Jul 30, 2026
Hi, this date shows the number when the redirected library was last parsed. But I get how it can be confusing. Maybe we can stop displaying some of these values here.
enesgules commentedon Jul 30, 2026
Thanks, removed
enesgules commentedon Jul 30, 2026
thanks, removed now
enesgules commentedon Jul 30, 2026
the content in deepwiki is slightly different than the ones in the repos, don't you think it's valuable as a source?
vitorsr commentedon Jul 31, 2026
It serves a similar purpose to Context7, and inherits the same issue as any other automatically generated documentation.
It is best to avoid anything other than ingesting first-party sources.
Muzakie-ID commentedon Sep 2, 2026
Add Libraries
Choose a documentation source to add to Context7.
Source
Website
URL
https://paymenku.com/merchant/api-docs
URL must be publicly accessible and point to official documentation.
Advanced
https://paymenku.com/merchant/api-docs
Only pages starting with this URL will be crawled. Useful for limiting the crawler to a specific section of the website.
Submit
Website score 1 below threshold 9
If you think this is a mistake, please open an issue.
alexanderkirtzel commentedon Sep 2, 2026
Duplicate: walkerOS is listed twice,
/elbwalker/walkeros(repo, claimed by me as maintainer, now with context7.json) and/websites/walkeros_io(the docs site, generated from the same repo). Searching "walkerOS" returns both. Please remove/websites/walkeros_ioand keep the repo entry. Thanks.enesgules commentedon Sep 4, 2026
Docs are behind a sign in page
enesgules commentedon Sep 4, 2026
I redirected the website to the repo and verified the repo while at it!
AstroPatty commentedon Sep 17, 2026
Found a duplicate, similar to others:
OpenCosmo is duplicated:
We should keep the repo (ArgonneCPAC/OpenCosmo) and get rid of the readthedocs site
enesgules commentedon Sep 28, 2026
Redirected, thanks for letting us know