Skip to content
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

fix: mixme Component Governance vulnerability #4078

Merged
merged 3 commits into from
Jan 27, 2022
Merged

Conversation

BruceHaley
Copy link
Contributor

Fixes #minor

Description

Fixes the high severity mixme vulnerability listed in these CG alerts:
https://fuselabs.visualstudio.com/SDK_v4/_componentGovernance/112352/alert/5657655?typeId=10422422
https://fuselabs.visualstudio.com/SDK_v4/_componentGovernance/112352/alert/5657656?typeId=10422422

Vulnerability: mixme 0.3.5. Recommended to upgrade to v 0.5.2.

Force dependency mixme to version 0.5.2.

Specific Changes

Add a resolutions section to the root package.json.

@BruceHaley BruceHaley requested a review from a team as a code owner January 25, 2022 00:35
@BruceHaley BruceHaley added the Area: Engineering Internal issues that are related to improving code quality, refactorings, code cleanup, etc. label Jan 25, 2022
@coveralls
Copy link

coveralls commented Jan 25, 2022

Pull Request Test Coverage Report for Build 1757442272

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.003%) to 84.545%

Totals Coverage Status
Change from base Build 1753569371: -0.003%
Covered Lines: 19667
Relevant Lines: 22035

💛 - Coveralls

@mrivera-ms mrivera-ms merged commit f04d672 into main Jan 27, 2022
@mrivera-ms mrivera-ms deleted the bruce/mixmefix1-24 branch January 27, 2022 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Engineering Internal issues that are related to improving code quality, refactorings, code cleanup, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants