Lint-staged is a popular npm package that helps developers automatically format and lint files that are staged for commit in Git. This ensures code quality and consistency across a project. Comparing version 7.2.0 with the previous stable version 7.1.3, developers will find subtle but important improvements. The core functionality remains the same: lint-staged runs configured linters and formatters against staged files, preventing commits with style issues or errors from entering the repository.
A primary focus for developers considering an upgrade should be the potential for bug fixes or performance enhancements incorporated between the two versions. While a detailed changelog would best reveal specific changes, upgrading from 7.1.3 to 7.2.0 likely involves standard dependency updates and minor code refinements to streamline the linting process. Both versions offer a solid foundation for integrating linting into Git workflows, leveraging dependencies such as Chalk for colorful console output, Execa for executing commands, and Cosmiconfig for configuration file loading. Developers already using lint-staged will find version 7.2.0 a worthwhile update to maintain a polished development workflow. The small increase in unpacked size, from 36750 to 36963, suggests a minimal impact on project size. Ultimately, staying up-to-date ensures access to the latest improvements and bug resolutions within the tool.
All the vulnerabilities related to the version 7.2.0 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.
