Audit vulnerabilities detected in the gulprename project on Tag: v1.2.2

[mahirkabir]

Issue: We detected vulnerable dependencies in your project by using the command “npm audit”:

npm audit report

glob-parent <5.1.2 Severity: moderate Regular expression denial of service - https://npmjs.com/advisories/1751 fix available via npm audit fix node_modules/glob-parent chokidar 1.0.0-rc1 - 2.1.8 Depends on vulnerable versions of glob-parent node_modules/chokidar glob-watcher >=3.0.0 Depends on vulnerable versions of chokidar node_modules/glob-watcher glob-stream >=5.3.0 Depends on vulnerable versions of glob-parent node_modules/glob-stream vinyl-fs >=2.4.2 Depends on vulnerable versions of glob-stream node_modules/vinyl-fs

yargs-parser <=13.1.1 || 14.0.0 - 15.0.0 || 16.0.0 - 18.1.1 Prototype Pollution - https://npmjs.com/advisories/1500 fix available via npm audit fix node_modules/yargs/node_modules/yargs-parser yargs 4.0.0-alpha1 - 12.0.5 || 14.1.0 || 15.0.0 - 15.2.0 Depends on vulnerable versions of yargs-parser node_modules/yargs gulp-cli >=2.0.0 Depends on vulnerable versions of yargs node_modules/gulp-cli gulp >=4.0.0 Depends on vulnerable versions of gulp-cli node_modules/gulp

9 vulnerabilities (4 low, 5 moderate)

To address all issues, run: npm audit fix

Questions: We are conducting a research study on vulnerable dependencies in open-source JS projects. We are curious:

1. Will you fix the vulnerabilities mentioned above? (Yes/No), and why?:
2. Do you have any additional comments? (If so, please write it down):

For any publication or research report based on this study, we will share all responses from developers in an anonymous way. Both your projects and personal information will be kept confidential.

Description: Many popular NPM packages have been found vulnerable and may carry significant risks [1]. Developers are recommended to monitor and avoid the vulnerable versions of the library. The vulnerabilities have been identified and reported by other developers, and their descriptions are available in the npm registry [2].

Steps to reproduce:

• Go to the root folder of the project where the package.json file located
• Execute “npm audit”
• Look at the list of vulnerabilities reported

Suggested Solution: Npm has introduced the “npm audit fix” command to fix the vulnerabilities. Execute the command to apply remediation to the dependency tree.

References:

2019. 10 npm Security Best Practices. https://snyk.io/blog/ten-npm-security-best-practices/.
2020. npm-audit. https://docs.npmjs.com/cli/v7/commands/npm-audit.