Version Details and Security Vulnerabilities

📦

husky

0.13.2

Comparision Betweeen 0.13.2 and 0.13.1

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 0.13.2 Details

Husky is a popular npm package designed to prevent developers from committing or pushing bad code by leveraging Git hooks. Versions 0.13.1 and 0.13.2 share the core functionality of intercepting Git actions like pre-commit, pre-push, and post-merge, allowing developers to run scripts that enforce code quality, run tests, or perform other validation steps before code is integrated. Both versions rely on familiar dependencies like chalk for terminal styling, is-ci to detect CI environments, normalize-path for path manipulation, and find-parent-dir to locate relevant project directories. They also share the same suite of developer dependencies including mocha and expect for testing, rimraf for file deletion, mock-fs for mocking file systems, and standard for JavaScript style checks. These help ensure the library itself is well-tested and adheres to coding standards.

The primary difference between the two lies in their release dates and a removed dependency. Version 0.13.1 was released on January 23, 2017 whereas 0.13.2 was released shortly after on March 2, 2017. Most notably the dependency pkg-ok was removed from the list of devDependencies from version 0.13.2. For developers, upgrading from 0.13.1 to 0.13.2 offers potentially improvements or bug fixes which aren't specified in the data, albeit minor, between the 2 releases. Given the rapid release cycle and identical dependency lists (besides the removal of pkg-ok), the update likely addresses specific niche scenarios or internal tooling improvements that streamline the development process. Developers facing issues with the dependency pkg-ok when using husky might be interested in upgrading.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.