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
Is it possible to upgrade the dependency Base64 from the current ~0.2.0 to latest (1.1.0)?
I have verified that Base64 is really only used once in http-browserify code and changing versions wouldn't break anything even though the semver indicates otherwise.
The root cause of my problems is that Base64 v0.2.0 offers WTFPL which is not white listed in our org. So static code analysis tools flag it as a policy violation. Base64 v 1.1.0 , on the other hand allows Apache 2.0 which is white listed in our org.
If there is a way to install the latest version of Base64 and make http-browserify point to this latest version then that could work as well. Note that webpack aliasing won't work since we need to pass static code analysis scrutiny which probably works off package-lock.json
The text was updated successfully, but these errors were encountered:
Is it possible to upgrade the dependency
Base64
from the current~0.2.0
to latest (1.1.0
)?I have verified that
Base64
is really only used once inhttp-browserify
code and changing versions wouldn't break anything even though the semver indicates otherwise.The root cause of my problems is that
Base64 v0.2.0
offers WTFPL which is not white listed in our org. So static code analysis tools flag it as a policy violation.Base64 v 1.1.0
, on the other hand allows Apache 2.0 which is white listed in our org.If there is a way to install the latest version of
Base64
and makehttp-browserify
point to this latest version then that could work as well. Note that webpack aliasing won't work since we need to pass static code analysis scrutiny which probably works offpackage-lock.json
The text was updated successfully, but these errors were encountered: