You can either run a signed app, in which case you wouldn't get those errors, or you can run an unsigned app with the "devmode" flag set, a debug token installed, and matching author and authorId fields in the bar-descriptor.xml file or whatever equivalent WebWorks uses. (I don't do WebWorks so I can't help with that.)
Note that this "devmode" thing is not the same as having the device in "development mode". Rather it's an option that is often available with the other SDK's packagers (e.g. blackberry-nativepackager) as "-devmode". It has the effect of setting the Application-Development-Mode field to True, in the MANIFEST.MF file of the .bar file.
If you try running an app where the .bar file has this Application-Development-Mode field set False or it's missing, but the .bar is unsigned or improperly, then you'll see that error.
As for how this all relates to Ripple, I have no idea... never used it. I'm just giving some background so you may be able to solve the rest of this yourself, maybe after reading some docs on the WebWorks/Ripple packaging tool(s).