In reply to Carl Hancock.

Carl: This is a service. It serves up blocks via an API and allows them to be included into the site. The javascript and CSS it serves up is service related, in so far that the javascript is the block. Also, we do allow CDNs for services when they are part of the same service, just like we would allow a plugin that talks to Facebook to get JS from fbcdn.net.

This is a legitimate service. Simple as that. It doesn't break any of our guidelines. Now, if it downloaded the JS into the site as files and such, then that would be much trickier. There would be security concerns there. That likely would break the guideline about installing executable code. But merely including some off-site javascript doesn't instantly disqualify a plugin from being in the directory. There's plenty of reasons for services to do exactly that. And there's plenty of reasons for the plugins team to scrutinize those individual cases, because if somebody is hosting some malicious JS code off site, then that should be noticed and disallowed.