Live data from Hacker News

GitHub's fake star economy

awesomeagents.ai

51–60 of 403 posts

Re: GitHub's fake star economy

#51
post #8

Earlier quoted context omitted.

> I look at the list of contributors Specifically if those avatars are cute animie girls.

> Specifically if those avatars are cute anime girls. I know you are half joking/not joking, but this is definitely a golden signal.

Positive or negative to you? Whenever I see more than one anime-adjacent profile picture I duck out.

Re: GitHub's fake star economy

#52
post #35

> VCs explicitly use stars as sourcing signals In my opinion, nothing could be more wrong. GitHub's own ratings are easily manipulated and measure not necessarily the quality of the project itself, but rather its Popularity. The problem is that popularity is rarely directly proportional to the quality of the project itself. I'm building a product and I'm seeing what important is the distribution and comunication inst…

Well, pretty sure that VCs are more interested in popularity than in quality so maybe it's not such a bad metric for them.

Yes, you're right, but popularity becomes fleeting without real quality behind the projects.

Hype helps raise funds, of course, and sells, of course.

But it doesn't necessarily lead to long-term sustainability of investments.

Re: GitHub's fake star economy

#53
> Jordan Segall, Partner at Redpoint Ventures, published an analysis of 80 developer tool companies showing that the median GitHub star count at seed financing was 2,850 and at Series A was 4,980. He confirmed: "Many VCs write internal scraping programs to identify fast growing github projects for sourcing, and the most common metric they look toward is stars."

> Runa Capital publishes the ROSS (Runa Open Source Startup) Index quarterly, ranking the 20 fastest-growing open-source startups by GitHub star growth rate. Per TechCrunch, 68% of ROSS Index startups that attracted investment did so at seed stage, with $169 million raised across tracked rounds. GitHub itself, through its GitHub Fund partnership with M12 (Microsoft's VC arm), commits $10 million annually to invest in 8-10 open-source companies at pre-seed/seed stages based partly on platform traction.

This all smells like BS. If you are going to do an analysis you need to do some sound maths on amount of investment a project gets in relation to github starts.

All this says is stars are considered is some ways, which is very far from saying that you get the fake stars and then you have investment.

This smells like bait for hating on people that get investment

Re: GitHub's fake star economy

#54
post #35

> VCs explicitly use stars as sourcing signals In my opinion, nothing could be more wrong. GitHub's own ratings are easily manipulated and measure not necessarily the quality of the project itself, but rather its Popularity. The problem is that popularity is rarely directly proportional to the quality of the project itself. I'm building a product and I'm seeing what important is the distribution and comunication inst…

Vast majority of mid level experienced people take stars very seriously and they won't use anything under 100 stars. I'm not supporting this view but it is what it is unfortunately. VCs that invest based on stars do know something I guess or they are just bad investors. IMO using projects based on start count is terrible engineering practice.

also and above all because it can be easily manipulated, as the research explained in the article actually demonstrates

Re: GitHub's fake star economy

#55
post #3

Honest question: how can VCs consider the 'star' system reliable? Users who add stars often stop following the project, so poorly maintained projects can have many stars but are effectively outdated. A better system, but certainly not the best, would be to look at how much "life" issues have, opening, closing (not automatic), and response times. My project has 200 stars, and I struggle like crazy to update regularly…

Much more important is who starred it. And are they selective about giving out stars or bookmarking everything. Forks is a closer signal to usage than stargazing.

Re: GitHub's fake star economy

#56
post #3

Honest question: how can VCs consider the 'star' system reliable? Users who add stars often stop following the project, so poorly maintained projects can have many stars but are effectively outdated. A better system, but certainly not the best, would be to look at how much "life" issues have, opening, closing (not automatic), and response times. My project has 200 stars, and I struggle like crazy to update regularly…

Many VCs are only doing one thing: how to use some magical quantitative metrics to assess whether a project is reliable without knowing the know-how. Numbers are always better than no numbers.

Re: GitHub's fake star economy

#57
post #24

I look at the starts when choosing dependencies, it's a first filter for sure. Good reminder that everything gets gamed given the incentives.

> I look at the starts when choosing dependencies, it's a first filter for sure. Unfortunately I still look at them, too, out of habit: The project or repo's star count _was_ a first filter in the past, and we must keep in mind it no longer is. > Good reminder that everything gets gamed given the incentives. Also known as Goodhart's law [1]: "When a measure becomes a target, it ceases to be a good measure". Essential…

> The project or repo's star count _was_ a first filter in the past, and we must keep in mind it no longer is.

Id suggest the first question to ask is "if the project is an AI project or not?" If it is, dont pay attention to the stars - if it's not, use the stars as a first filter. That's the way I analyse projects on Github now.

Re: GitHub's fake star economy

#58
post #56
post #3

Honest question: how can VCs consider the 'star' system reliable? Users who add stars often stop following the project, so poorly maintained projects can have many stars but are effectively outdated. A better system, but certainly not the best, would be to look at how much "life" issues have, opening, closing (not automatic), and response times. My project has 200 stars, and I struggle like crazy to update regularly…

Many VCs are only doing one thing: how to use some magical quantitative metrics to assess whether a project is reliable without knowing the know-how. Numbers are always better than no numbers.

Honestly I don't know if that's true. Picking up on vibes might be better than something like GitHub stats.

Re: GitHub's fake star economy

#59
https://x.com/garrytan/status/2045404377226285538

“gstack is not a hypothetical. It’s a product with real users:

75,000+ GitHub stars in 5 weeks

14,965 unique installations (opt-in telemetry, so real number is at least 2x higher)

305,309 skill invocations recorded since January 2026

~7,000 weekly active users at peak”

GitHub stars are a meaningless metric but I don’t think a high star count necessarily indicates bought stars. I don’t think Garry is buying stars for his project.

People star things because they want to be seen as part of the in-crowd, who knows about this magical futuristic technology, not because they care to use it.

Some companies are buying stars, sure, but the methodology for identifying it in this article is bad.

Re: GitHub's fake star economy

#60
post #3

Honest question: how can VCs consider the 'star' system reliable? Users who add stars often stop following the project, so poorly maintained projects can have many stars but are effectively outdated. A better system, but certainly not the best, would be to look at how much "life" issues have, opening, closing (not automatic), and response times. My project has 200 stars, and I struggle like crazy to update regularly…

I wonder if there's a more graph oriented score that could work well here - something pagerank ish so that a repo scores better if it has issues reported by users who themselves have a good score. So it's at least a little resilient to crude manipulation attempts

GitHub has all kinds of private internal metrics that could update the system to show a much higher signal/quality score. A score that is impervious to manipulation. And extremely well correlated with actual quality and popularity and value, not noise.

Two projects could look exactly the same from visible metrics, and one is complete shell and the other a great project.

But they choose not to publish it.

And those same private signals more effectively spot the signal-rich stargazers than PageRank.

Post reply on HN