Sadly, the scenario that the successor feature is intended to prevent has very much become reality in the past. The creator of Luacheck (Peter Melnichenko) passed away a couple of years ago, and ever since then the GitHub repository has been in a state of limbo. Multiple unofficial forks have come and gone, but Peter's is still the first result on Google if you search "luacheck". It isn't even possible to change the README or pin an issue to get people's attention about the primary fork; to this day people are still posting issues to the old repo.
And Luacheck is "the" Lua static analysis tool that pretty much everyone uses, so it's a very significant problem.
And Luacheck is "the" Lua static analysis tool that pretty much everyone uses, so it's a very significant problem.
https://github.com/mpeterv/luacheck/issues/198