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

meow@9.0.0 dependencies security advisory #7051

Closed
nathanaelytj opened this issue Jul 6, 2023 · 2 comments
Closed

meow@9.0.0 dependencies security advisory #7051

nathanaelytj opened this issue Jul 6, 2023 · 2 comments

Comments

@nathanaelytj
Copy link

What minimal example or steps are needed to reproduce the bug?

  1. Install stylelint
  2. Do npm audit

What minimal configuration is needed to reproduce the bug?

{
    "extends": [
        "stylelint-config-standard",
        "stylelint-config-standard-scss",
        "stylelint-config-recommended-vue"
    ]
}

How did you run Stylelint?

stylelint src/**/*.{css,scss,vue}

Which Stylelint-related dependencies are you using?

{
        "stylelint": "^15.10.0",
        "stylelint-config-recommended-vue": "^1.4.0",
        "stylelint-config-standard": "^33.0.0",
        "stylelint-config-standard-scss": "^9.0.0",
}

What did you expect to happen?

No security advisory warning

What actually happened?

There is security adivsory: GHSA-c2qf-rxjj-qqgw
Because dependency with meow

Do you have a proposal to fix the bug?

I'm reading that this issue will be fixed with #5291
Because dependabot bump #5463 closed with comment

Is there any solution for this advisory? Or we wait for issue #5291 ?

@mattxwang
Copy link
Member

Thanks for submitting an issue! We just merged in #7043, and will likely release it ASAP; this should resolve the advisory (and the original issue), it's not necessary to wait until #5291. Keep an eye out for the next release!

@mattxwang
Copy link
Member

Quick double-comment, but I've just cut a new release of Stylelint that should resolve the security advisory. Updating to 15.10.1 should resolve this issue.

With that in mind, I'm going to close this as complete; if you have a follow-up, feel free to re-open!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants