-
Notifications
You must be signed in to change notification settings - Fork 15
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
fix: 🐛 fix prototype pollution #58
Conversation
Hey @AdamGold thanks for making this PR! I remain unconvinced this is really a security issue. Additionally, if we were to consider this a security issue, where does the line get drawn? See also #57 |
Hey @keithamus! I definitely agree that this is a controversial vulnerability. Full disclosure - I work for Snyk, and we have dealt with quite a few of these. I understand your point, I would just like to clarify that the examples you've given - I think that this is the main reason for which this PR could be useful, and the line should be drawn there. With that being said, I am fine with you closing this PR if you still think we should not implement these checks. BTW I can not see the README warning anymore, has it been removed? (edit: sorry did not notice it was not merged!) |
The README warning was not merged, as no one has approved it yet (it's sitting here: #57). I'd like to hear from other members of @chaijs/core about this - perhaps @meeber or @lucasfcosta? |
Any news on this? |
@meeber or @lucasfcosta could you give an update on this? looks like an improvement to me. so why not merge it? |
Please use PR #60 Because it contains this fix code in addition of tests and needed update tool config for git workflow |
@keithamus as @kckst8 approved this PR. are we ready to merge, release etc..? 🙂 |
If someone can review and fix, it will be great! |
Released as |
For reference - the fix was merged in #60 |
No description provided.