The current maintainers are actively removing data that doesn't meet the "Alexa 200K" "requirement", and other PRs have been closed as "not in Alexa 100K".
https://github.com/2factorauth/twofactorauth/search?q=alexa&...
If this were a project I'd started and saw the new maintainers doing what they are, I'd be livid.
I cannot fathom the scenario where it makes sense to remove correct, useful information like this.
Seen this sort of stuff before. I'm betting that the maintainers are just overwhelmed with PRs for something that is essentially a side project for everyone involved. The solution to this sort of thing is to reduce maintenance burden.
They're given a PR with all the information needed, exactly as they requested it. They literally just have to click merge, and it's done.
Instead, they add their own manual steps of arbitrary Alexa ranking checks, and now, going back through existing entries to check them against Alexa, not just now, but in the past as well.
This whole exercise is creating work for them, not reducing it.
As mentioned, one has been merged, but with incorrect information. The company in question (VentraIP) has actually got a better document about this now (https://ventraip.com.au/faq/article/two-factor-authenticatio...), but I'm honestly beyond done with the current maintainers of that repo so I'm not willing to add further info to the PRs.