-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/192 #193
base: feature/187
Are you sure you want to change the base?
Feature/192 #193
Conversation
- Related OWASP#192 ``` cookie-parser ~1.4.4 → ~1.4.5 debug ~2.6.9 → ~4.1.1 express ~4.16.1 → ~4.17.1 http-errors ~1.6.3 → ~1.7.3 morgan ~1.9.1 → ~1.10.0 ```
- Related OWASP#192 - Added depedency `[email protected]` - Added main config file
- Related OWASP#192 - Added dev dependency `[email protected]` - Added npm tasks for linting
- Related OWASP#192 - Added dev dependencies `[email protected]` & `[email protected]` - Added npm tasks for testing
- Updated testing dependencies ``` @testing-library/jest-dom ^4.2.4 → ^5.1.1 @testing-library/react ^9.3.2 → ^10.0.1 @testing-library/user-event ^7.1.2 → ^10.0.0 ```
- Added jest to eslint rules - Linted files
- Related OWASP#192 - Added watch and CI support - Missing coverage and snapshot update
Hey @KoolTheba this is awesome! |
Hi @lirantal ! |
@KoolTheba when and if we do that migration - will it come with the exact same set of vulnerabilities in the new stack? |
Hi @lirantal ! |
@KoolTheba apologies, hard to keep up with many slacks and GitHub notifications. So what I mean is that we should maintain the current state of vulnerabilities as is demoed on the NodeGoat project right now. It is ok if we have different ways to exploit them, but the same set of vulnerabilities that are documented today in the project's tutorial should be kept. Is that the case for this PR? |
ping @KoolTheba |
Hi @lirantal ! |
Thanks for replying. I wasn't participating at the time it was demo'ed. Any chance there's a recording that easily verifies that? |
Hi @lirantal !
If you want to take leadership on it, feel free to add the changes you mentioned. And if you need a contributor/maintainer, let me know, very happy to collaborate with you if you guide the next iteration. |
IMPORTANT
PR Backlog (see #192)
Notable changes
React api
[email protected]
[email protected]
[email protected]
&[email protected]
React client
Changelog