No comments yet.
Once the students moved on I continued to think about and would occasionally get asked about the tool. So I picked it back up and slapped an API on it and exposed it via HTTPS POST and GETs.
I am generally looking for feedback. Probably more about the issues associated with dependence on Open Source libraries - the risks derived as software atrophy happens. But what are your ideas about the metainformation that is sitting in a software project's source history.
I've considered doing some ML-y stuff with the commit history, but haven't really found the right things there yet.
Here are some links to the details:
* Library: https://github.com/gtri/lowendinsight * API: https://rapidapi.com/quency-ai-quency-ai-default/api/lowendi... * API Source: https://github.com/quency-ai/lowendinsight-get * CLI: https://github.com/quency-ai/lowendinsight-cli/releases * CLI Source: https://github.com/quency-ai/lowendinsight-cli * Demo - GitHub Trending Repos: https://demo.lowendinsight.dev/gh_trending
I've capped the number of requests at RapidAPI, but if you really think the tool is useful I can issue you freer, more unlimited access by request.
Let me have it HN. And thanks in advance.