>Unrelated, but the fact that the developer doesn't get the extension AMO approved and uses eval() all over the place should give some pause as well.
He does, it is in the official add-on site, but their approval process is slow, and a few times a Firefox update has broken it and I've had to download the update from the dev's site because it takes a long time to update on the official site.
Just because it's on the site doesn't mean that it's approved... it's marked experimental by the developer to not require a full review with the caveat that any experimental extension is inherently more risky than a reviewed one. The developer lists a few reasons why they don't do the full review and one of those is that they use eval() and that the review takes longer than they deem acceptable. I just said it should give a little bit of pause not that you should wholesale reject using their extension. I just looked over his code and it's quite a lot of code for something that should be fairly straightforward.
He does, it is in the official add-on site, but their approval process is slow, and a few times a Firefox update has broken it and I've had to download the update from the dev's site because it takes a long time to update on the official site.