A suggestion addressing the ABANDONED REPOSITOREIS

I have always been surprised, how GitHub defeats its purpose to be the place where the development happens. What I mean - plenty of repositories are being abandoned by original developers. This is what will eventually happen to every [99%] repository maintained by single person, because no-one lives forever.

However, the surprising is how GitHub ignores this and leaves abandoned repositories as is, causing hundreds of thousands of peoples frustration in every month because of stopped development. People are then manually try to hire programmers or find alternative repositories and recode their programs to accomodate other (maintained) library…
And why GitHub (that giant) doesn’t care of this?

  1. Not only GitHub shows a top notice in abandoned repo, that “There is actively maintained Fork of this repo”, but it doesn’t even have a functionality to EVEN JUST SEE THE ACTIVE FORKS of the repo (and shame on you, someone individual has made a custom tool to do that - https://techgaun.github.io/active-forks/index.html ). However, doing “tricky ways” to find out the active fork even is not acceptable. At least, there should be a title in abandoned repos that “here are some active forks” (which will be chosen by Github algorithm to decide which one is active fork).

  2. The second suggestion is that, after 2 years are passed on repo withuot any further update, this should be a absolute sign of the stopped development. When anyone creates a repo, there should be a checkbox saying "Do you allow the repo to have continued development by community if you abandon it [ ✓ ](by default turned “check” that checkbox). So, after 2 years pass, the most active contributor (or the most active fork’s maintainer) should be able to get privillege to “merge pull requests” into main repo.

Thus will will not see thousands of peoples rewriting and redoing work every time when author no-longer interested in software development, even though there are hundreds of users. I don’t see any justification why GitHub doesn’t care so much during all these years.