Audit vulnerabilities detected in the createhash project on Tag: v1.2.0

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

trim-newlines <3.0.1 || =4.0.0
Severity: high
Regular Expression Denial of Service - https://npmjs.com/advisories/1753
fix available via `npm audit fix`
node_modules/trim-newlines
meow 3.4.0 - 5.0.0
Depends on vulnerable versions of trim-newlines
node_modules/meow

2 high severity vulnerabilities

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/.
2021. npm-audit. https://docs.npmjs.com/cli/v7/commands/npm-audit.

Comienza en la raíz del proyecto, en package.json, y ejecuta npm audit para confirmar las vulnerabilidades reportadas en las dependencias trim-newlines y meow. Aplica la corrección de dependencias sugerida y vuelve a ejecutar npm audit; se considera terminado cuando las vulnerabilidades reportadas de gravedad alta están resueltas sin romper el proyecto.

Escrito por el modelo de indexación a partir del texto del issue.