npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mimik/git-hooks

v2.1.1

Published

Git hooks helper for better development

Readme

git-hooks

Example

import { commitCheckMsg, validateCommit } from '@mimik/git-hooks';
// or
import gitHooks from '@mimik/git-hooks';

git-hooks~validateCommit(branchName, commitMsg) ⇒ Object

Validates a commit message against a branch name's JIRA ticket number.

The branch name must contain a JIRA ticket in the format PROJ-123- (with a trailing dash), matching the convention for JIRA-generated branches (e.g. feature/BES-1219-my-branch). The commit message must start with the same ticket number followed by a space and a description of at least 10 characters.

Kind: inner method of git-hooks
Returns: Object - Result with valid flag and error message (null when valid).

| Param | Type | Description | | --- | --- | --- | | branchName | string | The current git branch name (must contain PROJ-123- pattern with trailing dash). | | commitMsg | string | The commit message to validate (must start with matching ticket number). |

Example

import { validateCommit } from '@mimik/git-hooks';
const result = validateCommit('feature/BES-1219-my-branch', 'BES-1219 implement user authentication');
// result: { valid: true, error: null }

git-hooks~commitCheckMsg([options]) ⇒ Promise.<null>

Checks the validity of the commit message against the current branch's JIRA ticket number. Reads the commit message from the file at process.argv[2].

Kind: inner method of git-hooks
Returns: Promise.<null> - Resolves with null on success. On failure, the process exits with code 1 (the promise never resolves).
Category: async

| Param | Type | Description | | --- | --- | --- | | [options] | object | Internal options for dependency injection (testing). | | [options.git] | function | Git client factory (defaults to simpleGit). |

Example

import { commitCheckMsg } from '@mimik/git-hooks';
// or
import gitHooks from '@mimik/git-hooks';