Oh for sure. Javascript itself is intrinsically vulnerable at the application level. This is just a fact of web design. I'm not saying this is bad, it's a nice exercise. I'm just saying it's not viable for real world deployment. Please correct me if I am wrong however, i'm usually the one breaking in, not making the door.
Any security check on the frontend side is just... the joke, maybe? All the verification should be done on the server-side. But for UX, it is a good idea to inform the user about the password's strength. Concerning "the real world deployment" I would not recommend reinventing the wheel and simply use any of the trustful production-ready libraries. Nonetheless, from the educational perspective, why not?
I don’t know enough about the subject matter to tell you one way or another. However, having my primary focus in learning right now be heavily JavaScript-Based, it’s cool seeing this type of thing both showcased and critiqued.
4
u/[deleted] Feb 10 '20
Why tho?