hover luceos wrote that it's up to the community to re-upload the extension. Of course care should be given to the license terms (MIT-licensed extensions can be re-published by anybody as long as the original license file is included, so it's usually fine). While there is no requirement for extension publishers to provide support, re-publishing an abandoned extension often comes with the expectation that the new developer will take on the care of the extension, so most developers like myself won't just re-publish an extension unless it's part of a paid job.
As the Flarum Foundation or staff member of the forum, there is unfortunately nothing we can do about deleted packages. Packagist and GitHub are the most popular way to distribute Flarum extensions and we can't prevent people from removing packages, even if the license allows re-distributing the code.
@BAANAN if you could delete the packages from Packagist or mark them abandoned it would be nice. Removing the package from GitHub but not Packagist creates all kinds of annoying issues since Packagist still believes the code can be found on GitHub. Packagist doesn't actually host any code, it just tells Composer to download the zipped files from GitHub.
In the future Flarum might have an extension marketplace where we have control over the distributed files, but this is still a long time away.
