Maybe? At this point I don't care enough to wade into that. A worse place, however, would be the Coveralls "Community" section. Of the five actual questions posted there, zero have been answered over a period of four months. (I had to use incognito mode to see this, due to the redirect loop noted above.)
Presumably, if one were comfortable with the perms they're now requiring, one would be happy with the service. I haven't given them the perms, so since they changed the service to require them I can't update my config in any way, or add new repos. I guess eventually I'll either figure out a new coverage service to use or I'll just handle my own coverage icons. It seems that an npm script could generate an svg icon based on the output of the coverage tool, and the readme could just point at that.
Whatever, it's free. I'll stop bitching.