-
Notifications
You must be signed in to change notification settings - Fork 124
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
Outdated packages with vulnerabilities #700
Comments
I have been going through the packages this morning, and here is my initial analysis: NPM PackagesDev Dependencies
Dependencies
|
I will now see if I can get these issue resolved and create a pull request if I'm successful. |
I've now updated all the packages and resolved all related issue. There are a few deprecation warning related to 'sass-mq' as the package is using some method that are soon to be removed from 'sass'. As far as I can tell, though, the whole package builds and all the npm scripts are working as expected. Let me know if you have any questions. |
I have just made a few more changes to this after testing the package in our WordPress install. I have just update how "react-select/async" and ajax from "rxjs" are used to bring them inline with the latests packages, however, it's still not working perfectly. I might not have any more time to work on this, so if anyone else is able to take this on, please let me know. |
We've been using this package for a number of years, but are currently seeing issues flagged up by dependabot.
Many of the NPM packages are outdated and have vulnerabilities.
Currently we're seeing 100 vulnerabilities:
I've started auditing the package to see if I can easily resolve these vulnerabilities, however, currently I'm seeing a number of deprecated packages used, so some if not all of these will need to be replaced.
There are also a number of packages that are no longer maintained.
We would like to continue using the package, however, these security vulnerabilities make that not an option for us at the moment.
I aim to complete my audit of the packages today, and will update this issue with my findings.
I will then see how feasible it is to resolve the vulnerabilities.
Do you plan to continue maintaining this package?
Is anyone else working on updating these packages?
If the package is going to be maintained,
I'm happy to help resolve these issues and get it back up and running.
Also, if there is someone who knows the package well, it would be very helpful to be able to discuss the packages that are currently used.
The text was updated successfully, but these errors were encountered: