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
Using the tool Snyk, I found that there is a license risk introduced by the package svgo within broccoli-svg-optimizer. This issue could limit the use of emer-svg-jar from a legal stand point. The root cause of this issue is a package called mdn-data introduced via the following package chain:
More details regarding the licensing risks introduced by this package can be found in Snyk's database here.
Reproduce the bug
Install snyk-cli locally
Navigate into the local ember-svg-jar project
Run snyk test --all-projects
Expected behavior
Snyk should not report a licensing risk when scanning this project.
Possible Solution
Upgrading svgo should resolve the issue as it will bump the version of mdn-data being used to a version that is not at a licensing risk. Sadly this would involve a major jump from the current svgo version of 1.3.0 to 2.0.0 or greater and a minimum Node version of 13 or greater as required my svgo V2.
The text was updated successfully, but these errors were encountered:
Hi friends. I'm pretty slammed lately and can't take this on. I believe the path forward is having us move to SVGO v2 entirely. Is anyone interested in volunteering to do this work?
🐞 Bug Report
Describe the bug
Using the tool Snyk, I found that there is a license risk introduced by the package
svgo
withinbroccoli-svg-optimizer
. This issue could limit the use ofemer-svg-jar
from a legal stand point. The root cause of this issue is a package calledmdn-data
introduced via the following package chain:[email protected] > [email protected] > [email protected] > [email protected] > [email protected] > [email protected]
More details regarding the licensing risks introduced by this package can be found in Snyk's database here.
Reproduce the bug
snyk-cli
locallyember-svg-jar
projectsnyk test --all-projects
Expected behavior
Snyk should not report a licensing risk when scanning this project.
Possible Solution
Upgrading
svgo
should resolve the issue as it will bump the version ofmdn-data
being used to a version that is not at a licensing risk. Sadly this would involve a major jump from the currentsvgo
version of1.3.0
to2.0.0 or greater
and a minimumNode
version of13 or greater
as required mysvgo V2
.The text was updated successfully, but these errors were encountered: