3 ms·

And which method should be used to determine code quality?

• PeeMcGee 2y ago
  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.
• est 2y ago
  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.
  • demaga 2y ago
    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.
    • arresin 2y ago
      Also tests, coverage and tests passing!
    • est 2y ago
      > since you can use other markers Yesh, surely I can, but how about https://github.com/trending https://github.com/trending ? It still uses "stars" are a sole marker, no? I don't think it's "good enough"?
• saagarjha 2y ago
  Definitely not stars lmao. Why would you want to use a measure of publicity as a measure of quality?
  • hulitu 2y ago
    > Definitely not stars lmao. Why would you want to use a measure of publicity as a measure of quality? It is Microsoft.
• michaelt 2y ago
  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