VeryNice!

I am trully love your enterpise soulution

Approved your one. Looks good!

Yeah, I get that, I stumbled across this translation after writing my own here. I wasn't sure if I should look at tidying this up since its been 4 months or publish a separate one. (I thought CW was supposed to warn me if I tried to create another translation for one that was already in progress. Well thats what the wiki said anyway)

My point was that people can easily hack a call like Math.random() (without qualified name).

kotlin.random.Random.nextDouble() is obviously a better one.

Would it make sense to use kotlin.random.Random.nextDouble() for the Kotlin translation since that seems to be more idiomatic to Kotlin than Math.random()? Or stick with Math.random() to keep the translations consistent?
Was going to translate this and found this existing translation.

Left some comments, please improve :)

0. Math.random() call is vulnerable, please use java.lang.Math.random(). Otherwise people can simply hack by creating object Math { fun random() }.
1. Please add more tests (like calling it more times to ensure the return value varies), as present in Scala translation.

Kotlin translation: https://www.codewars.com/kumite/5c12419c8a2d874c9c00006e?sel=5c12419c8a2d874c9c00006e

Already reported. Please scroll a bit further to see my request.

The problem seems to be when any r, g or b value is between 10 and 16 it drops the preceeding '0' eg. 10(dec) -> A(hex) instead of 0A(hex). So a quick fix is to just add a case for when the value is between 10-16 and drop that 0.

Kotlin : The sample tests expect 6 digit hex values but the random tests are expecting 5. A RGB hex needs 6 digits to be valid. This error is only occuring when the value is between 10 and 16, e.g. it will expect 'F' instead of '0F'.

A hack is to put an additional check but it should be this way.