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

commit-naming-enforcement

v0.0.1

Published

A convenient way to check commit namings

Readme

commit-naming-enforcement

A commit name verification tool

Installation :

Install your favorite git hook tool. (Recommended : Husky)

In your package.json, you can then start with your preferred hook : node -e require('commit-naming-enforcement')

Exemple (using Husky) :

    ...
    "husky": {
        "hooks": {
            "pre-commit": "npm run precommit-msg && npm run eslint",
            "pre-push": "node -e require('commit-naming-enforcement')"
        }
    }
    ...

Usage :

A few config keys are availible, all setted/listed in defaults.js, and can be overrided in the project's package.json you need to use the corresponding key : commit-naming-enforcement

package.json :

    ...
    "scripts": {}, 
    "commit-naming-enforcement": {
        "enabled" : true,
        "regexToSeparateTitleAndBody" : ".",
        "regexToCheckTitle" : ".",
        "titleNotCorresponding" : "Commit title faulty, please see https://github.com/angular/angular/blob/master/CONTRIBUTING.md for guidelines"
    }
    ...

Config keys

Enabled, Boolean

If false, the commits won't be verified

regexToSeparateTitleAndBody, Regular expression

This RegExp is used to separate the commit title and its body.

Then the title shall be parsed for conformity.

If you wish to do a validation check on all the commit (body + title), you can use this regex : "(\n|.)*"

regexToCheckTitle, Regular expression

The validation check. In the case of no-match, it is considered as an error.

Meaning the evaluated 'title' must match the regex for the commit to be accepted

titleNotCorresponding, String

The error message that will be displayed if the previous regexToCheckTitle fail