Lint-staged is a popular npm package that helps developers automatically lint files that are staged in Git, ensuring code quality and consistency. Version 7.2.1 is a patch release following version 7.2.0, offering enhancements and bug fixes to refine the developer experience. While both versions share the core functionality of linting staged files, there are subtle differences in their dependencies and specific features that impact developers.
One notable difference is the jest-validate dependency. Version 7.2.1 upgrades this dependency to version 23.5.0, whereas version 7.2.0 uses version 23.0.0. jest-validate is responsible for validating the configuration options provided to lint-staged. The size unpacked also differs. 7.2.1 has a size of 37342 while version 7.2.0 has a size of 36963. Both versions maintain the core dependencies like pify, chalk, execa, listr, and cosmiconfig, which are essential for promises, terminal styling, executing commands, creating task lists, and managing configuration files, respectively.
For developers considering upgrading, the transition from 7.2.0 to 7.2.1 should be relatively smooth. The primary benefit lies in the updated jest-validate dependency, which may introduce improvements in configuration validation and provide more robust error handling. Furthermore, any bug fixes and performance tweaks incorporated in the patch release will contribute to a more stable and reliable linting process. It's always advisable to review the changelog or release notes for a comprehensive understanding of specific changes and potential impact on existing workflows.
All the vulnerabilities related to the version 7.2.1 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.
