Even without this, I don't think the claim that "memccpy() comes relatively close" to safe string manipulation can be taken seriously if it doesn't even null terminate the destination. That's a pretty core requirement.
(I mean, of course it doesn't null terminate given its intended usage, but that's what it would need for that claim.)
it should be
Not the end of the world but just another subtly bugged implementation..This illustrates the issue..
Notice in the code below how it wipes out the dest string at char 0 when we supply buf[1]
if we didn't supply buf[1] the zero gets written at buf[size_t_max]