markdown guide

There are different factors, some of them are:

  1. It should have more feature request opened.
  2. Contributors should be active, it's not important there is daily commit but history will provide enough information that its active.
  3. Github stars will help you also to know about the popularity of the project.
  • I agree number of stars will encourage more contributors to join the projects, so it's really an effective factor to qualify a project.

  • Pull Request is only helpful if there's actually communication and colloborator to help that feature landed effectively on time, because in many cases, the implementer really needs helps from the community.


It has no open bug reports and still more than one user.


But you could eventually try it and contribute back to make it greater ?


I usually go with stars and latest commits, if I am in doubt I check also the issues activity (when a issue was opened, resolved, etc)


Thanks. Could you explain more why you consider those as the most important factors ?

  • Stars show the popularity of this repository in the community.
  • Latest commit show how active the contributors and members, sometimes I check the commits of other branches like dev because not always master is the main branch.
  • Issues show how active the community is

That's about it I think

Too much issues also mean the instability of the project ?
Of course i prefer too much issues than having no issues at all. It just means that the project demand is high !

It means that demand is high as you say, I wouldn't say instability.
Take React as an example there are 276 opened issues there...

Sure. Some maintainers are just lazy enough to close useless and out-of-date issues ;)

Classic DEV Post from May 28

Those silly mistakes we all make

Silly mistakes happen to us all.

Truong Hoang Dung profile image
I hate technical debts, very much. Learning to clean debt out of my life. now has dark mode.

Go to the "misc" section of your settings and select night theme ❀️