+1 on the name, agreed.

WRT to the params, I'm in two minds about this, and not strongly for or against either.
One could argue that as there is only _one_ option at the moment, then a) a param is ok, and b) having the plural `options` is slightly wrong.
But, it does allow forward changes (more options etc) to not breaking backwards compatibly, so +1 to this, I'll update.

BTW, although it will be better with Ruby2, I don't think this gem will drop 1.9.3 support any time soon, so a shame, but I don't think we can take advantage of those here.