News for hackers. Stuff that matters.
Re:4.5M (Suspected) Fake Stars in GitHub by demaga on Friday January 03, 2025 @12:55AM (#42582940)
And which method should be used to determine code quality?
Re:4.5M (Suspected) Fake Stars in GitHub by est on Friday January 03, 2025 @01:39AM (#42583166)
If that's a problem, then what method should be used to rank repos?

If "stars" were the only metric we can find, then people should stop complaining "fake" stars.

Re:4.5M (Suspected) Fake Stars in GitHub by demaga on Friday January 03, 2025 @01:49AM (#42583209)
I'm with the other commenters on this issue. Stars are good enough as a marker, since you can use other markers (like # of contributors and recent commits) to make your own mind regarding quality of a repo.
Re:4.5M (Suspected) Fake Stars in GitHub by est on Friday January 03, 2025 @02:51AM (#42583547)
> since you can use other markers

Yesh, surely I can, but how about https://github.com/trending ?

It still uses "stars" are a sole marker, no? I don't think it's "good enough"?

Re:4.5M (Suspected) Fake Stars in GitHub by bn-l on Friday January 03, 2025 @02:29AM (#42583408)
Also tests, coverage and tests passing!
Re:4.5M (Suspected) Fake Stars in GitHub by PeeMcGee on Friday January 03, 2025 @01:04AM (#42582974)
An easy one would be to promote projects that look like actual useful projects that contain code. Most of the ultra-starred things I see are awesome lists or otherwise non-useful markdown listicles and blogs.
Re:4.5M (Suspected) Fake Stars in GitHub by saagarjha on Friday January 03, 2025 @06:29AM (#42584705)
Definitely not stars lmao. Why would you want to use a measure of publicity as a measure of quality?
Re:4.5M (Suspected) Fake Stars in GitHub by hulitu on Sunday January 05, 2025 @04:01PM (#42605000)
> Definitely not stars lmao. Why would you want to use a measure of publicity as a measure of quality?

It is Microsoft.

Re:4.5M (Suspected) Fake Stars in GitHub by michaelt on Friday January 03, 2025 @08:44AM (#42585585)
It's simple.

Code quality is (Number of stars + number of forks * median number of commits per fork + 10 * number of closed issues + 100 * number of open issues + 3 * number of dependent packages + 0.01 * number of installs in the last 30 days) * number of commits in the last 100 days * number of core contributors active in the last 7 days / percentage of lines of code with no test coverage / (1+the number of open CVEs in dependencies) * the vibe factor