Any other fixes needed? If not, vote that the kata is ready, please.

I agree, trying to lock down every avenue of cheating is more trouble than it is worth. If cheating does become a problem by degrading the visibility of good solutions to learn from, then the kata should be updated. In the same vein, I think katas should avoid imposing extraneous requirements to sanitize function inputs as the extra code to do so can obscure an otherwise awesome solution.

My opinion about this type of cheating is that it will be addressed by the site eventually. People's solutions are out there for everybody to see, and I expect there to be some sort of mechanisms to deal with this. Either by letting users flag/expose a cheating solution, and/or by static analysis of the solutions.

Which makes me not want to worry about it, since it is extra effort for little value...

I added a random unit test.

Looks like everyone thinks there are minor issues with this kata. Any suggestions beyond the hardcoding of the test fixture?

That does apply to the most katas here. In my opinion the users should not try to cheat themselves. Otherwise they miss the point of solving a kata. It's not about solving all of them in no time and being #1 of the leaders list. It's about practising common problems and learning. And maybe trying to solve the same problem multiple times with different ideas.

I updated the description so it isn't one long sentence. With that, I think this is ready to come out of beta.

Thank you, I have been doing too much coffeescript lately.

Yes, that threw me too.

Fixed