I've discovered that an open source project I was counting on, was nearly dead by seeing its issues: 80 blockers, 100 criticals, 800+ majors, and a decreasing number of contributions over years.
Another project, I had trouble using it. It has 2,600 issues (it doesn't prioritize them) opened.
Does a declaration, a guarantee, some kind of good practice label exists, that affirms that an open source team is especially committed to correct the issues its software encounters (assuming they have endorsed them to be of gravity Major or more), prior to evolution of features? Or, at least, to correct them with an especially high frequency? With thresholds or something else?
Will avoid making mandatory for the user to provide a test case (or even an Unit Test, I saw that) before studying a bug, which is (in my mind) the major cause of never starting correcting issues.