Lint-staged is a popular npm package that helps developers automatically format and lint files staged in Git, ensuring code quality and consistency before commits. Comparing versions 7.2.2 and 7.2.1, developers will notice a subtle but potentially significant change in the dependencies. Version 7.2.1 includes app-root-path as a dependency, which is absent in version 7.2.2. While seemingly minor, this alteration could influence how the library resolves file paths and interacts with the project's root directory.
Both versions share a robust set of core dependencies, including pify, chalk, execa, and listr, crucial for asynchronous operations, colorful console output, executing commands, and creating elegant task lists. The presence of jest-validate highlights the package's commitment to configuration integrity, and cosmiconfig suggests support for diverse configuration file formats, allowing seamless integration into various projects.
Developers considering an upgrade should evaluate whether the removal of app-root-path affects their specific use case. If your project relies on lint-staged for complex path resolution scenarios, testing the upgrade thoroughly is recommended. Lint-staged improves development workflows by automating code quality checks, freeing up developers to focus on code, making it easy to deliver high-quality, consistent code.
All the vulnerabilities related to the version 7.2.2 of the package
Regular Expression Denial of Service (ReDoS) in cross-spawn
Versions of the package cross-spawn before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
