Skip to content

chore: update bin-version-check #58

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Florian-Schoenherr
Copy link

Needed to fix this vulnerability in yo:
image

Signed-off-by: Florian-Schoenherr <florian.schoenherr99@gmail.com>
@Logicer16
Copy link
Contributor

The changelog of version 5.0.0 of bin-version-check lists becoming pure ESM as a breaking change. Have you checked here to make sure there isn't anything else that needs changing? Have you tested it?

@vikasjagdale92
Copy link

@Florian-Schoenherr could you please merge this change. I need this change, as we are getting security vulnerability issue.

@crazy-tush
Copy link

@Florian-Schoenherr - Please merge the "bin-version-check" related PR changes as we are getting security vulnerability issue.

@JoshuaKGoldberg
Copy link

JoshuaKGoldberg commented Mar 20, 2025

This is blocked on #61, as noted in #58 (comment).

security vulnerability

If you have an actual security vulnerability, please go through the standard security reporting flow. https://yeoman.io/blog/security-policy-update

If your issue is just that some tool is yelling about you about a general report, you'll want to check if that report actually impacts you.
https://www.joshuakgoldberg.com/blog/please-stop-sending-me-nested-dependency-security-reports ❤️

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

Successfully merging this pull request may close these issues.

5 participants