You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mason-js dependency is unmaintained and frozen, but still currently used inside of vtshaver. It has been unmaintained since 2018. For a while it seemed like mason-js would again see maintenance (enough that security issues related to out-of-date binaries and mason-js JS dependencies could be mitigated). But, in effect, mason-js not been maintained since 2018 and therefore I think it is critical to acknowledge this and take action downstream (here).
So, my recommendation is to remove the dependence on mason-js in vtshaver.
To do this would involve:
Removing mason-js from the package.json
Removing the mason-versions.ini
Implementing an alternative method for fetching up to date and reliable versions of dependencies that are currently being installed by mason-js
The text was updated successfully, but these errors were encountered:
The
mason-js
dependency is unmaintained and frozen, but still currently used inside ofvtshaver
. It has been unmaintained since 2018. For a while it seemed likemason-js
would again see maintenance (enough that security issues related to out-of-date binaries andmason-js
JS dependencies could be mitigated). But, in effect,mason-js
not been maintained since 2018 and therefore I think it is critical to acknowledge this and take action downstream (here).So, my recommendation is to remove the dependence on
mason-js
invtshaver
.To do this would involve:
mason-js
from thepackage.json
mason-versions.ini
mason-js
The text was updated successfully, but these errors were encountered: