This is a great point. Let me address your concerns: About being able to see the code: most definitely. Every "script" consist of zero or more requirements, on

This is a great point. Let me address your concerns: About being able to see the code: most definitely. Every "script" consist of zero or more requirements, one or more executions and zero or more validations. Each one is, in the end, a shell script with placeholders. You will be able see the scripts source code online and also "clone" the script to your account (not a git clone but an actual hard copy) and dump it locally using our ruby gem that talks to our API. We will record another screencast soon about how we create new scripts and how we upload them. About flagging scripts: we don't want to enforce any formal approval process, but we want the community to be able to flag scripts for malicious code. Another indication of quality may be the number of people who deployed it and/or watched it. We're open to suggestions and feedback on how we could improve it without making it an administrative burden. In the end, you're responsible for what you're installing in your server -- being it manually or through a script. Thanks for such a quality feedback. Please keep'em coming.