No. This kata just requires an O(n log n) algorithm to solve, you don't need any require() calls to work. An O(n^2) one will fail the test though.

this needs an answer though

Sorry, I seem to have only edited in one of them.

The actual code length limit is 120 chars but in the sample test it's 150 chars.

You don't have a test for characters at the end of "Can someone explain" that aren't spaces, for example "Can someone explainable" may work in some people's code

So, how could someone use this and what should I do to stop this? Is this like require, so I'd do process.binding = null

Thank You!

Approved!

That's enough for me

I think I have made all the changes you wanted, can you check? I put encrypt in a function now due to anti-cheat.

Some minor things

• This is unnecessary because we aleady banned the Function::toString

  Test.expect(encrypt.toString(), `function (k, s) {
    return f(k, s);
  }`);

• You forgot to add // FINALTEST flag

• Put let encrypt and all below into // Preload some tools
  Because
  A. let encrypt is modifiable, put it before those anti-cheat code and it would become 'const' (dont forgot to remove the let so it would be a global variable)
  B. Put function name(){} in a closure and it would not be covered, like

console.log(a)
function a(){ /* first */ }
function a(){ /* second */ }

Thank you for all your help, do you think this issue is now resolved?

@bdupau Yes, it my own code (look at the PascalCase things ), which is only applied in my latest JS kata
And i'm not sure if it is still vulnerable

Yes i guess, just dont submit, or just try in sample test, or in the edit panel