the current unsigned validator only supports integer values, if you try to validate (float) 5.9 it will return false. the inline documentation says checks if given value is a valid unsigned integer, so this is not really the bug.

the problem is that if you try to validate "five" it would return true ;-)

and because of the general name of this validator one would expect that it supports floats as well :-)

i wrote a patch which supports both int and float values and which does not return true if the value is "five"