Automic VaultAutomic Vault

brew

Install claude-hooks with Homebrew

Hook system for Claude Code. Version 2.4.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install claude-hooks

local Homebrew formula metadata

overview

Package summary

Hook system for Claude Code

Commands and aliases

  • claude-hooks

history

Project history and usage

claude-hooks is a TypeScript-oriented setup tool for Claude Code hooks. Its official README describes it as a CLI that generates `.claude/settings.json` hook configuration and typed TypeScript handler files for Claude Code lifecycle events.

Project history

The npm package was first published in July 2025, after Claude Code's hook system had become a documented extension point. The project focuses on one friction point in that system: turning JSON hook payloads and shell-command handlers into a typed TypeScript development environment.

The README documents generated files under `.claude/hooks/`, including `index.ts`, `lib.ts`, and `session.ts`, plus `.claude/settings.json`. It also requires Node.js 18+ for the CLI and Bun for running hooks.

Adoption history

Distribution is source-backed through npm and Homebrew. The npm registry records 32 versions and published version 2.4.0, while Homebrew packages the same 2.4.0 release from the npm registry.

The evidence supports a niche but clear role: claude-hooks is not a general Claude Code replacement; it is a helper for users who are already adopting Claude Code's official hook lifecycle and want TypeScript types and scaffolding.

How it is used

Users run `npx claude-hooks` or install it globally with npm, then run `claude-hooks`. The tool creates Claude Code hook configuration and TypeScript handlers that can inspect typed payloads for events such as PreToolUse, PostToolUse, Notification, and Stop.

The official Claude Code hooks reference documents the underlying event model, including command, HTTP, prompt, and MCP hooks, matcher groups, JSON stdin payloads, and hook decisions. claude-hooks builds on that official mechanism.

Why package nerds care

claude-hooks is package-nerd interesting because it packages a type layer around an AI-agent lifecycle API. Instead of every team copying shell scripts and JSON snippets, it gives the hook surface a generated project structure and a package-manager install path.

It also shows how fast companion packages formed around Claude Code's configuration files: the package's value is not the hook runtime itself, but the typed developer experience around an official extension point.

Timeline

  • 2025-07: npm registry records the first `claude-hooks` publication.
  • 2025-08: npm registry records published version 2.4.0 after 32 published versions.
  • 2026: Homebrew formula `claude-hooks` packages version 2.4.0 from the npm registry.

Related projects

  • Claude Code's official hooks system is the extension point claude-hooks configures.
  • Bun is required by the README for running generated hooks.
  • TypeScript is the language layer used for typed payloads and handlers.
  • claude-cmd and Claude Code Templates are related Claude Code configuration companion tools.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

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
.claude/settings.json

executables

Installed executables

CommandKindExposureNote
claude-hookscliglobal 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 version2.4.0
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/johnlindquist/claude-hooks

install metadata

Package metadata

Package keybrew:claude-hooks
Version2.4.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/claude-hooks
Homepagehttps://github.com/johnlindquist/claude-hooks
Repositoryhttps://github.com/johnlindquist/claude-hooks
Upstream docshttps://code.claude.com/docs/en/hooks
LicenseMIT
Source archivehttps://registry.npmjs.org/claude-hooks/-/claude-hooks-2.4.0.tgz
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

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
  • package relationship graph
  • package version freshness
  • package-page enrichment