-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
update depedency unset-value to latest version #28
base: master
Are you sure you want to change the base?
Conversation
Can the maintainer please merge this in? |
@jonschlinkert Can this please be merged? The vulnerability on |
@wtgtybhertgeghgtwtg Can you merge this? |
I am not a maintainer, so I cannot. |
it will be great if this get merge |
I am not a maintainer of this repo. Hence it is not possible to be of help.
Apologies.
…On Wed, 16 Nov 2022 at 07:00, krudos ***@***.***> wrote:
it will be great if this get merge
—
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHBVSLV4YTCBIUDRZWVKDTWIQ2NHANCNFSM5SILJTCQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It appears @jonschlinkert has not done anything in Github since 2021. Not sure what that means, but he seems to not be maintaining a presence here any more. Seems like this is never going to be fixed unless there is some way he can grant someone else maintainer access or Github can. Does anyone know if there is a process for this? (I'm just sick of the constant warnings from Snyk when this could have been fixed 8 months ago). |
Reached out on Twitter to see if he can help us out. |
anyone got LinkedIn premium? He's on there and active |
Apparently @jonschlinkert is active on Github. Could you please merge this PR? Thanks! |
Can we please merge this PR? |
👍🏻 for the merge |
#Issue:
The unset-value [email protected] poses a vulnerability.
https://security.snyk.io/vuln/SNYK-JS-UNSETVALUE-2400660
#Solution:
Upgrade the package to the latest version to mitigate this vulnerability.
Please let me know if more information / explanation would be required.