Lint-staged is a popular tool that helps developers maintain code quality by running linters only on files staged for commit. This ensures that only clean code makes its way into the codebase, preventing regressions and maintaining consistent formatting. Comparing versions 7.1.3 and 7.1.2 reveals subtle but important updates. While both versions share a core set of dependencies for tasks like file manipulation (lodash, micromatch), configuration (cosmiconfig), and running commands (execa), the key distinction lies in the jest-validate dependency. Version 7.1.3 upgrades jest-validate from version 22.4.0 to 23.0.0. This update likely brings improvements in validation performance, new validation rules, or bug fixes within the configuration validation process. For developers, this translates to a potentially more robust and faster configuration experience. Although seemingly minor, such dependency updates can improve the tool's overall stability and reliability. Both versions offer the same core functionality, linting staged files according to a user-defined configuration, leveraging tools like ESLint and Prettier. This allows for automated code formatting and style enforcement before committing changes. These versions depend on a similar set of devDependencies useful for local development, debugging and testing. The update from 7.1.2 to 7.1.3 is beneficial for developers using lint-staged, as it incorporates improvements and fixes within the jest-validate library, which contributes to a potentially smoother and more reliable experience when managing project configurations and can potentially make debugging even easier.
All the vulnerabilities related to the version 7.1.3 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.
