We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Recently the bin-wrapper dependency was added, which then was modified to use the @mole-inc fork since that one is maintained.
bin-wrapper
This still uses bin-check which depends on execa 0.7 which has a vulnerability (OS Command Injection in execa)
https://www.npmjs.com/package/bin-check https://www.npmjs.com/package/execa
I've opened a ticket with mole-inc to see if they can fork bin-check as well and remove that old dependency mole-inc/bin-wrapper#10
The text was updated successfully, but these errors were encountered:
I would be interested in this as well
Sorry, something went wrong.
#291
Also,execa is used in many other packages, and uses cross-spawn (sindresorhus/execa#578)
execa
cross-spawn
No branches or pull requests
Recently the
bin-wrapper
dependency was added, which then was modified to use the @mole-inc fork since that one is maintained.This still uses bin-check which depends on execa 0.7 which has a vulnerability (OS Command Injection in execa)
https://www.npmjs.com/package/bin-check
https://www.npmjs.com/package/execa
I've opened a ticket with mole-inc to see if they can fork bin-check as well and remove that old dependency mole-inc/bin-wrapper#10
The text was updated successfully, but these errors were encountered: