Lint-staged is a popular npm package that helps developers automatically lint files staged in Git, ensuring code consistency and quality before commits. Version 7.3.0 brings incremental improvements over the previous stable release, 7.2.2. While both versions share identical dependencies and devDependencies suggesting consistent core functionality and developer tooling, several subtle changes distinguish them. The core functionality around leveraging linters against staged files remains the same between the two versions.
The primary difference lies in the dist object, which describes the packaged release. Version 7.3.0 exhibits a slightly larger unpackedSize (38603 bytes compared to 37450 bytes in 7.2.2), suggesting optimizations, minor feature additions, or potentially bug fixes within the codebase. Developers should also bear in mind the release date: 7.3.0 was published on 2018-09-20, substantially later than 7.2.2 (2018-08-12). This temporal gap indicates the newer version benefits from bug fixes which might have been reported and addressed in the interim.
For developers already using lint-staged, upgrading to 7.3.0 offers the benefits of a potentially refined and more stable codebase. A slightly larger unpackedSize may indicate valuable updates or bug fixes. While no dependencies were visibly changed between versions, upgrades usually bring improvements, so it is recommended to use the newest one.
All the vulnerabilities related to the version 7.3.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.
