Show HN: GitGauge – A Way to Try Tell If a Repo Is Authentic(github.com)
github.com
Show HN: GitGauge – A Way to Try Tell If a Repo Is Authentic
https://github.com/Davey2Waveyy/gitgauge
2 comments
This is a neat idea. Definitely needs tuning.
- I tried it on a repo that has very obvious boosting tells, like 99% of stars from week old or less accounts and it had higher trust signal than my own very much so real project. The issue to star ratio gave 5/5 despite the issues being core contributor created.
- In same vein as above, it seems to prefer open issues over closed ones in the scoring.
Have you considered scoring contributors/authors/issue creators separately to use as a proxy, instead of measuring the core things that are being gamed?
- I tried it on a repo that has very obvious boosting tells, like 99% of stars from week old or less accounts and it had higher trust signal than my own very much so real project. The issue to star ratio gave 5/5 despite the issues being core contributor created.
- In same vein as above, it seems to prefer open issues over closed ones in the scoring.
Have you considered scoring contributors/authors/issue creators separately to use as a proxy, instead of measuring the core things that are being gamed?
I appreciate the feedback!
That’s a great point, will work on trying to score not just the repo but author use too.
That’s a great point, will work on trying to score not just the repo but author use too.
I'd love to hear some feedback!
The part I’m least confident about is the heuristic. Right now it uses stars, forks, watchers, and open issues. I’d be really interested in where people think that breaks down, especially for niche repos, old repos, or heavily used internal-tool style projects.