Add Stars count filter

[kjsman]

Example: stars:1000 only queries codes of repositories which starred more than 1k.

This would help researchers to find specific patterns from open sources projects.

[warengonzaga]

I love the idea of it...

[DamianFekete]

Add starts count filter... or be able to sort by the number of stars.

[p0]

That's a good idea! We currently use indicators like star/watcher/fork counts (and many others) to rank and score results, so you should tend to see results from repos with more stars higher up. It would be possible to expose those in the search query syntax too. I'll take it to the team.

[wumpus]

I see that the advanced search now allegedly has the ability to filter by star count, but it only searches the names of repos. And doesn't seem to work. I was hoping to search code and then filter by star count, so I could open issues against a bunch of repos that need an API update.

[intrigus-lgtm]

I'd also be interested in filtering by star count and also fork count.
For security research it might also be interesting to filter by projects that are older than xyz days/years to filter inactive/abandoned projects.

[pluraltouch]

that is a shame. Not only one, but two reasons: a) it is basic functional requirement to sort hundreds of result by some quality rank. b) As for any result item, there is a single star number attribute, and it is simple to get, there would be no technical difficulty to implement this.

In general neither the syntax help, neither the announcement mentions the term "sort". I am wondering how on earth the team thinks that a search functionality can be useful without sorting facility?

[Wladefant]

It is already implemented: an example

[DamianFekete]

HttpServletRequest stars:>10 doesn't find any code.

[cpctaylo]

I get

The stars qualifier is not supported when searching code. Try searching for repositories instead?

[goproslowyo]

I didn't realize it supported the range pattern. Exactly what I was looking for: stars:100..5000

[wumpus]

But it's still only searching repo names. If you look at commits in the result, there's a warning:

The stars qualifier is not supported when searching commits. Try searching for repositories instead?

[jin-yng]

Any way we could get this feature on code searches? I have the case where I am searching for a particular usage pattern and would like to find a well-established, production tested method.

[jin-yng]

A sort of greatest to least would be most helpful.

[zeddysoft]

Do we have any update on this yet

[thecatontheceiling]

I also would love this feature to be added

[hatlesswizard]

We are still waiting for this feature to be added

[remmons-r7]

This feature would be a huge deal for me if added. +1 :) thank you!

[GermanAizek]

Microsoft still hasn't made this feature, it seems they have completely abandoned Github as actively developed product. People have been asking since 2021, but the function has been gone for 4 years. But it really would be the most convenient function.

[shinybrightstar]

Hi Community 👋

I am able to see repositories filtered by the number of stars, as shown in this screenshot below. If you have a different experience, please comment in this discussion.

We appreciate your patience as we work toward a solution.

[ouuan]

We are talking about code search, not repository search. See above

[shinybrightstar]

Okay. Thanks for the clarification!

[amitschendel]

+1, would really love to see this feature added

[ahmedelq]

It's 2025 and honestly, I'm surprised GitHub hasn't shipped this feature yet, especially given how straightforward it seems.

I often find myself searching for code examples to learn from or to solve specific problems. However, with so many results, it's hard to sift through and find a production-grade codebase. That's my main motivation for adding the following features:

• Star‑count: Let us do something like stars:>1337 or explicitly sort by stars. Repo search has it. Why not code search?
• Fork‑count: Similarly for fork something like forks:>42.
• Project age filters: A created:<YYYY‑MM‑DD>, pushed:>2025-07-01, or age:>1y to exclude abandoned or brand‑new repos.
• Sort syntax: We need explicit sort: (sort:stars, sort:forks, sort:updated, etc...) or similar syntax for result ranking.

Would love to see this prioritized and shipped ASAP.

[larrasket]

Can't believe this is not supported.