I also opened up a issue on the GitHub Repo but I think it may be favorable to document how a package can be added to the plugin.
With this, the community could do the heavy lifting of finding and maybe even compiling the packages and adding packages would go faster.
Of course this introduces the problem of verifying that a package wasn't modified from the source. For that I propose that for packages that were already found compiled, the link to the checksum could be given (so not the checksum directly but the link of where to find the checksum in combination with the package itself) to verify the package.
For packages that need to be compiled manually because they are not available in the public package lists, I propose, instead of adding the compiled package directly, which can't be easily verified, to open a Issue with the necessary commands to compile it. So that would be the commands to download the source, extract it, build and compile the package, and package it again for the plugin.
Link to the issue