The point is not to have the script directly install the program (e.g. getting the binary, putting it where it needs to be, and making a desktop file), but to have the script be used as a wrapper for any of the methods you mentioned above. This would allow for a more consistent installing experience, and in the future, a unified CLI. It would also be better for the reasons mentioned in my post.

It does have a discussion system at the moment where you can comment on a script, but there is no system to rate the script and have the total of all the ratings combined.

I have, but I think it would be a bit too expensive on my VPS, but might use it if my site ever catches on. I have also considered using something like Try, but it isn’t a full sandbox.

Thank you for the feedback. I think I will remove the voting system for now while I figure out of solution. I will probably not be adding the user reputation system, unless I figure out a way to do it without facing the problems you have mentioned. As for collaboration, I will add a feature allowing app maintainers to set whether or not non-maintainers can add scripts without maintainer permission. Thank you again for the feedback, it was very useful!

1. It is different from a package manager because it isn’t platform specific because you can add scripts for any distro or architecture.
2. It isn’t really comparable to something like that because it just stores and runs bash scripts to install stuff.
3. It can install any app, from anywhere, not just specific to zsh.
4. It’s mostly convenience. Also, not all websites have a script to remove once installed, or automated ways to update.

It is possible to make the website think I am using chrome and windows, but I don’t want to get in trouble for cheating. Even if I use degoogle Chromium it still won’t allow me because I use Linux.