Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Understanding of the criteria "outdated"? #154

Open
vgw-chriskruger opened this issue Feb 1, 2023 · 1 comment
Open

Understanding of the criteria "outdated"? #154

vgw-chriskruger opened this issue Feb 1, 2023 · 1 comment

Comments

@vgw-chriskruger
Copy link

I'd like to understand by which criteria a framework is judged as "outdated"? It's a loaded classification so I think it is fair to be transparent about the criteria by which the frameworks are evaluated.

@flosse flosse added the question label Feb 2, 2023
@flosse
Copy link
Owner

flosse commented Feb 2, 2023

I'd like to understand by which criteria a framework is judged as "outdated"?

That's a very good question. To be honest, there are no fixed criteria yet, but I am very interested in what the community thinks about it. I can think of a few aspects that we might want to consider:

  • latest release
  • last commit
  • open PRs not commented on
  • outdated dependencies
  • unaddressed safety issues
  • bugs

What do you think?

It would be pretty cool if the information could be retrieved via an API to automate the process.

@flosse flosse pinned this issue Oct 27, 2023
This was referenced Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants