Automic VaultAutomic Vault

brew

Install commitlint with Homebrew, Nix, winget

Lint commit messages according to a commit convention. Version 21.2.0 via Homebrew; verified 2026-07-01.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install commitlint

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#commitlint

nixpkgs package indexes · pkgs/by-name/co/commitlint/package.nix · source: api.github.com

Windows

Windows Package Managerverified · 92%
winget install --id Commitlint.Commitlint -e

Windows Package Manager source index · Commitlint.Commitlint · source: cdn.winget.microsoft.com

overview

Package summary

Lint commit messages according to a commit convention

Commands and aliases

  • commitlint

history

Project history and usage

commitlint is a Node.js CLI and library family for checking commit messages against a convention, most commonly Conventional Commits.

Project history

The project is part of the conventional-changelog GitHub organization and presents itself as the linting half of the Conventional Commits workflow. Its README describes three core package-culture concerns: being a good Commitizen companion, sharing configuration through npm, and integrating with conventional-changelog.

Adoption history

The npm package history for `@commitlint/cli` dates to 2017. The official README describes commitlint as stable and used in various projects, with setup paths for local Git hooks and CI. The project also documents shareable npm configurations, which made commit rules reusable across JavaScript monorepos and organizations.

How it is used

commitlint is usually run as a commit-msg hook through tools such as Husky, or in CI against commit ranges. Its configuration files and package.json field make it fit naturally into Node package workflows.

Why package nerds care

For package maintainers, commitlint matters because it turns release-note and versioning conventions into a lintable contract. It is often paired with conventional-changelog, release automation, and Commitizen-style prompts.

Timeline

  • 2017: npm records public `@commitlint/cli` releases.
  • 2020s: Official docs describe local-hook, CI, shared-config, and prompt workflows.
  • 2026: npm continues to publish 21.x releases.

Related projects

  • commitlint is closely related to Conventional Commits, conventional-changelog, Commitizen, Husky, and npm shareable configuration packages.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for commitlint. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./commitlint.config.js./commitlint.config.cjs./commitlint.config.mjs./commitlint.config.ts./commitlint.config.cts./commitlint.config.mts./.commitlintrc./.commitlintrc.json./.commitlintrc.yaml./.commitlintrc.yml./.commitlintrc.js./.commitlintrc.cjs./.commitlintrc.mjs./.commitlintrc.ts./.commitlintrc.cts./.commitlintrc.mts./package.json

executables

Installed executables

CommandKindExposureNote
commitlintcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version21.2.0
manager updated2026-07-01
local dataok
upstreamnot checked
latest detectednot detected

https://commitlint.js.org/#/

install metadata

Package metadata

Package keybrew:commitlint
Version21.2.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/commitlint
Homepagehttps://commitlint.js.org/#/
Repositoryhttps://github.com/conventional-changelog/commitlint
Upstream docshttps://commitlint.js.org/
LicenseMIT
Source archivehttps://registry.npmjs.org/commitlint/-/commitlint-21.2.0.tgz
Last updated2026-07-01T12:49:47Z
Pulseupdated
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecommitlint
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

commitlint

nix profile install nixpkgs#commitlint
  • normalized package name match
  • Matched by: Commitlint
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/co/commitlint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
winget95%

Commitlint.Commitlint

winget install --id Commitlint.Commitlint -e
  • normalized package name match
  • Matched by: Commitlint
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Commitlint.Commitlint from https://cdn.winget.microsoft.com/cache/source.msix

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment