Perhaps put a warning in the name since the folks who don’t read the docs are the ones you’re trying to protect?
For example: Math.RandomNotCrypto()
When someone uses that in production for cryptographic purposes (and, yes someone is going to do that), they have to wear a dunce cap to the office for a month.