If someone approved their own PR in our team they would have some explaining to do, approving your own PR in an Open Source project - SMH
In this case abe33 has the 75% of the commits, someone else 15% and the rest is a bunch of people with 1% or less.
With our server toolkit in a project I work on, we have 2 devs and 5 active users, with the devs being 2 of those, but we still manage to at least put every change in a PR, with a minimum review and comment time of 24 hours unless it's a security issue or major bug fix.
It's not hard, and it makes you actually justify your change and have talented second eyes point out minor bugs or edge cases to you.
Direct commits are only used for version bumps for the auto build/release thingy.