Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lucthienphong1120/form-validate
Form validate user input for securing webapp
https://github.com/lucthienphong1120/form-validate
form form-validate form-validation forms input-validation javascript js security user-input validation
Last synced: about 2 months ago
JSON representation
Form validate user input for securing webapp
- Host: GitHub
- URL: https://github.com/lucthienphong1120/form-validate
- Owner: lucthienphong1120
- License: epl-2.0
- Created: 2022-04-09T07:51:27.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-02-06T16:01:27.000Z (almost 2 years ago)
- Last Synced: 2023-03-05T18:54:07.792Z (almost 2 years ago)
- Topics: form, form-validate, form-validation, forms, input-validation, javascript, js, security, user-input, validation
- Language: HTML
- Homepage: http://ltp.crfnetwork.cyou/form-validate/
- Size: 43 KB
- Stars: 9
- Watchers: 1
- Forks: 1
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# form-validate
Form validate with js (2 ways), see the example below
+ https://www.ltp110.tk/form-validate/index
+ https://www.ltp110.tk/form-validate/index2More other types, see at [Issues](https://github.com/lucthienphong1120/form-validate/issues)
## Not All Solutions are Equal
Input validation is an important layer of security that all production-level applications should have. However, no matter how ‘perfect’ your input validation is for your specific use case, there simply are limitations to all kinds of security implementations - and input validation is not exempt from it.
You cannot make your application fully XSS-proof through input validation alone. Controls may be put in place at the input level that may lessen the attack surface of the application, but it doesn’t fully remediate it. Full remediation of an XSS vulnerability in your application requires additional layers of defenses, such as mitigation on the browser-level (via secure cookies, content-security-policy headers, etc.) and escaping and purifying user-provided input.