Getting operational risk for Mahapps 2.4.10 in black duck scan #4533
mehakbansal28
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Despite updating MahApps.Metro from version 1.3.0 to the latest 2.4.10 to address an operational risk flagged in our Black Duck scan, we are still encountering vulnerability warnings.
Could someone help explain why the latest version continues to trigger this operational risk?
Dependency Tree:
Mahapps:2.4.10
ControlzFx- 4.4.0 (which is not latest)
Microsoft.xaml.behaviours.wpf: 1.1.19 (not latest)
Thanks
Beta Was this translation helpful? Give feedback.
All reactions