I found a review by Peter Greenburg which says:
This extension is NOT WORKING, IT *DOESN'T* PROTECT YOU!
Disabling ScriptNo and controlling JS with in the Chrome settings isn't an alternative, either: I've noticed on a couple of sites (which only work in Firefox if I allow some 3rd party domains in Noscript) that they work in Chrome without the need to allow scripting for those 3rd party sites. In other words: If you allow JS for a specific site, you're obviously also allowing all 3rd party scripts.
1. Script blocking in ScriptNo is unreliable. Either that relatively new API it's using is still crap or ScriptNo itself is flawed.
2. Controlling JS in the Chrome settings is ridiculous as you always automatically allow 3rd party scripting.
That's really not the degree of control which I expect from my browser. I will stick with Firefox for the time being.