@commitlint/cli versions 6.0.5 and 6.0.4 are both command-line interfaces designed to lint commit messages, ensuring they adhere to a defined style or set of rules. This promotes consistency and clarity within a project's commit history, improving collaboration and maintainability. Both versions share identical core dependencies such as meow for command-line argument parsing, chalk for colored terminal output, get-stdin for reading from standard input, and Lodash utilities (lodash.pick, lodash.merge) for object manipulation. They also rely on babel-polyfill for compatibility with older JavaScript environments and, crucially, depend on @commitlint/core for the actual linting logic.
The development dependencies are also identical, including tools like xo for linting the codebase, ava for testing, and various utility libraries for file system operations (tmp, execa, mkdirp, rimraf, sander, pkg-dir). Babel (babel-cli, babel-register, @commitlint/preset-commitlint) is used for transpiling code, cross-env manages environment variables across platforms, and concurrently aids in running multiple development tasks. Testing dependencies are also consistent with @commitlint/test, string-to-stream and @commitlint/utils.
The primary difference lies in the version field and the releaseDate. Version 6.0.5 was released shortly after 6.0.4, on the same day. This suggests that 6.0.5 likely contains bug fixes or very minor improvements over 6.0.4, as the dependency tree and the developer tooling setup remain unchanged. For developers, upgrading from 6.0.4 to 6.0.5 is recommended likely to acquire those little fixes and improvements. The package empowers developers to enforce standards, improving the quality of project history and facilitating smoother collaboration.
All the vulnerabilities related to the version 6.0.5 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.
