@commitlint/cli version 5.2.8 introduces subtle but significant updates compared to the previous stable version, 5.2.6. Both versions serve the crucial role of linting commit messages, ensuring adherence to established conventions for cleaner project histories and improved collaboration. While the core goal remains the same, the dependency updates in 5.2.8 offer noticeable refinements.
Notably, 5.2.8 replaces the general lodash dependency found in 5.2.6 with more specific, tree-shakable lodash modules: lodash.pick and lodash.merge. This change is valuable for developers concerned about bundle size, as it allows only the necessary utility functions to be included in the final build, potentially leading to performance improvements especially in larger projects. The update to @commitlint/core from "^5.2.6" to "^5.2.8" suggests improvements and bug fixes within the core linting logic.
Furthermore, a minor change appears in cross-env, which went from 5.1.2 to 5.1.1. This might involve bug fixes or adjustments for cross-platform compatibility, but without further details remains a minor change.
Developers upgrading from 5.2.6 to 5.2.8 should appreciate the refined dependency management and focus on potential improvements within the core linting process. Keep in mind to verify compatibility on each of your environments. Staying up-to-date with @commitlint/cli ensures that your project benefits from the latest improvements in commit message consistency and potentially a slightly smaller bundle size thanks to the more specific lodash dependencies.
All the vulnerabilities related to the version 5.2.8 of the package
Uncontrolled Resource Consumption in trim-newlines
@rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.
Prototype Pollution in lodash
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
Prototype Pollution in lodash.merge
Versions of lodash.merge before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.6.1 or later.
Prototype Pollution in lodash.merge
Versions of lodash.merge before 4.6.2 are vulnerable to prototype pollution. The function merge may allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.6.2 or later.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Prototype Pollution in lodash.mergewith
Versions of lodash.mergewith before 4.6.1 are vulnerable to Prototype Pollution. The function 'mergeWith' may allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.6.1 or later.
Prototype Pollution in lodash.mergewith
Versions of lodash.mergewith before 4.6.2 are vulnerable to prototype pollution. The function mergeWith may allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.6.2 or later.
dot-prop Prototype Pollution vulnerability
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
