SpiderBasic

When creating a Chrome extension it's necessary to add 'unsafe-eval' to the "content_security_policy", this suggests eval() is being used somewhere under the hood. Google discourages the use of eval() in extensions because it creates security issues. I think the policy for Chrome apps is even stricter and the 'unsafe-eval' override isn't available.