@commitlint/cli versions 6.0.0 and 6.0.1 are both command-line tools designed to lint commit messages, ensuring they adhere to a defined set of rules and conventions. This promotes consistency and improves the clarity of project history, making it easier for teams to collaborate and understand changes. While both versions share a core functionality and a significant portion of their underlying dependencies and development tools, a closer examination reveals subtle yet important distinctions.
The key difference between the two versions lies within their internal dependencies. Version 6.0.1 has a dependency on "@commitlint/core":"^6.0.1" which is slightly newer than version 6.0.0 which depends on "@commitlint/core":"^6.0.0". While this delta might seem trivial, upgrades to core dependencies often include bug fixes, performance improvements, or new feature additions. For developers using @commitlint, this suggests that upgrading to version 6.0.1 could provide a more stable and potentially enhanced linting experience.
Both versions rely on popular packages like "meow" for command-line argument parsing, "chalk" for colored output, and "lodash" utilities for data manipulation. Their development environments are also equipped with tools like "xo" for linting, "ava" for testing, and "babel" for transpilation. These shared tools indicate a commitment to quality and modern JavaScript practices. Developers leveraging @commitlint/cli can expect a well-supported and actively maintained library that integrates seamlessly into existing JavaScript projects.
All the vulnerabilities related to the version 6.0.1 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.
