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

nomnom is no longer supported and generates security vulnerabilities #142

Open
domenic opened this issue Jun 28, 2023 · 1 comment
Open

Comments

@domenic
Copy link

domenic commented Jun 28, 2023

Just an FYI: https://www.npmjs.com/package/nomnom says "This package has been deprecated", and running npm audit generates various security vulnerability warnings.

I am sure none of them are actually exploitable, so it's not a big deal. But I thought maybe you would want to have an issue on the record for moving to a supporting command-line arguments processor. (I tend to use yargs but Node 16+ has a built-in parser that might work.)

@DmitrySoshnikov
Copy link
Owner

@domenic thanks, yes, we'll need to migrate to the modern approach used today for this (both yargs and native Node should work). Would appreciate a PR in case.

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

No branches or pull requests

2 participants