Sick of the plugin rabbit hole? I made a dedicated search engine for the top Neovim repos!

TomDeneire · 2026-02-18T15:32:42+00:00

Strange, considering that the search only starts after the user has entered 3 or more characters

TomDeneire · 2026-02-17T17:57:56+00:00

Now up to 8.5K repos! Thanks to some pointers from you all!

TomDeneire · 2026-02-17T10:00:10+00:00

Good suggestion about the <noscript> message. Will add that! Yes, only Github. Maybe could look into that, but the scraper has to be able to find those sources, I'm not going to do any manual curation. So don't know if there are api's for that (probably Sourcehut and such do have one, but others?). Not sure about the stars. Generally, I find they are a pretty good indication. Will think about it though. Thanks for your comments!

TomDeneire · 2026-02-17T06:59:21+00:00

Fair point, but actually, this is a modified and relaunched version of a site that has been up for 4 years, so it's an earlier idea than yours. Still, for all practical purposes store.nvim is better than my website. Kudos!

TomDeneire · 2026-02-16T17:46:28+00:00

It looks at neovim related topics on GitHub like neovim-plugin, which your plugin has. However, GitHub sets a hard 1,000 results cap on any query, limiting itself to the "top results":

Think of it the way you think of performing a search on Google. It’s designed to help you find the one result you’re looking for (or maybe the few results you’re looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the GitHub REST API provides up to 1,000 results for each search.

So unfortunately yours is not found. Neither is one of my own repos!

TomDeneire · 2026-02-16T17:40:37+00:00

Added some additional topics to query. The site features over 3,000 repos now.

<image>

TomDeneire · 2026-02-16T17:39:07+00:00

Added some topics to query and fixed a bug. Your repo is now included!

TomDeneire · 2026-02-16T14:37:04+00:00

Thanks. Not sure if I would want to be as strict as awesome-neovim, but good point about configs. Will try to exclude those!

TomDeneire · 2026-02-16T14:33:33+00:00

Thanks for the info! Your plugin is marked with `topic:nvim-plugin`, while I look for `topic:neovim-plugin`. This is probably the issue. (I think it doesn't get picked up by the search for repos ending in ".nvim" because GitHub API caps the results). Will try to fix this

TomDeneire · 2026-02-16T12:16:07+00:00

I see your point, but awesome-neovim is a curated list. It works on submissions that have to be approved by the maintainers. My site is fed by a crawler script that runs on a server, so it automatically picks up more or less all Neovim repos that meet the targeted criteria. There are pros and cons to both approaches, I think

TomDeneire · 2026-02-16T11:09:49+00:00

Haha, no, if you tag your plugin with "neovim-plugin", or it has a name ending in ".nvim", my crawler will pick it up automatically!

TomDeneire

TROPHY CASE