@commitlint/cli, a popular tool for linting commit messages, released version 4.2.0, building upon the previous stable version 4.1.1. The core functionality of linting commit messages remains consistent, aiming to enforce standardized and readable commit histories. Key dependencies like meow, chalk, lodash, get-stdin, and babel-polyfill are retained, ensuring continued compatibility and feature support.
The most notable difference lies in the updated dependencies. @commitlint/core, the core logic for commit linting, jumps from version 4.1.1 to 4.2.0, indicating potential bug fixes, new rules, or improvements to existing linting capabilities. The dev dependency @commitlint/utils also sees an update from version 3.1.1 to 4.2.0, suggesting enhancements in utility functions used within the development and testing environment of the CLI. These updates are important for developers as they ensure that the linting rules and supporting utilities are aligned and up-to-date.
Developers upgrading to 4.2.0 should review the @commitlint/core and @commitlint/utils changelogs to understand the specific changes introduced. While the core usage of the CLI likely remains unchanged, these updates provide opportunities to leverage new linting rules or benefit from performance optimizations in the underlying libraries. The consistent use of testing frameworks like xo and ava ensures ongoing code quality and stability. The release on October 14, 2017, followed shortly after version 4.1.1 (released on October 9, 2017), suggesting a focused effort to rapidly iterate and improve the package.
All the vulnerabilities related to the version 4.2.0 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.
Command Injection in lodash
lodash
versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
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.