@commitlint/cli version 6.0.2 represents a minor update over its predecessor, version 6.0.1, primarily focusing on dependency upgrades and refinements rather than introducing significant breaking changes or new features. Both versions serve the same core function: linting commit messages to ensure they adhere to a predefined set of rules, promoting consistency and clarity in project commit history.
Key differences lie in the updated dependencies. Version 6.0.2 sees @commitlint/core bumped to "^6.0.2" (from "^6.0.1"), @commitlint/test bumped to "^6.0.2" (from "^6.0.0"), @commitlint/utils updated to "^6.0.2" (from "^5.1.1") and execa upgraded to "0.9.0" (from "0.8.0"). These dependency bumps likely include bug fixes, performance improvements, and potentially new features within those individual packages. Furthermore babel-preset-commitlint moved from "^5.2.0" to "^6.0.2" which could influence the compatibility with certain Javascript setups. Also dependency-check was upgraded from "2.9.2" to "2.10.0".
For developers using @commitlint/cli, these changes translate to potentially improved stability and performance. Upgrading to 6.0.2 is recommended to benefit from the latest bug fixes and enhancements within the core linting logic and its supporting utilities, especially considering security vulnerabilities are a pressing concern nowadays in javascript developement. The upgrades to the devDependencies might also improve developer experience.
All the vulnerabilities related to the version 6.0.2 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.
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.
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.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
