Very useful project. I wanted to deploy a Java application as a Windows Service and thought to write a tool to generalize that to any kind of daemon process. Then realized surely it's been done before, and a quick search found yours!
But shocked by the organization of this repo. I'm avoiding hyperbole here that would sound mean. Would be much better if it had a doc folder, a src folder with the source files ready to build, build instructions and scripts. And then you tag releases under which you deploy the build output(s) as assets. As it is with a bunch of zip files, someone coming here doesn't know what they need to download for their specific need.
For example, I just needed the artifacts to run the application. Do I need to download all the _run zips? No I think, just srvstart/srvstart_run.v110.zip. Typically you would deploy this as a release asset. If someone needs the docs, they can just download those (or you could zip a separate asset), and if someone needs the source, then they clone the repo.