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

validate-branch

v1.2.7

Published

A CLI tool to validate Git branch names using Conventional Branch guidelines.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

silent_watchersilent_watcher

Keywords

gitbranchbranch-validationnaming-convention cliconventional-branchversion-control

Readme

validate-branch

Checked with Biome Commitizen friendly License: MIT

A CLI tool to validate Git branch names using Conventional Branch guidelines. This package ensures that your branch names follow consistent naming conventions—supporting core branches like main, master, and develop, as well as structured feature, bugfix, hotfix, and release branches.

Table of Contents

Installation

Install the package globally using npm:

npm install -g validate-branch

Or add it as a development dependency in your project:

npm install --save-dev validate-git-branch

Usage

Command Line

Once installed, run the CLI command in your Git repository:

validate-branch

The tool will fetch the current Git branch name and validate it against the conventional naming rules. If the branch name is valid, you'll see a success message; otherwise, an error message will guide you to use the correct format.

Git Hooks Integration

You can integrate this tool with Git hooks to enforce branch naming on every commit or push. For example, using Husky:

npx husky add .husky/pre-push "validate-branch"

Branch Naming Conventions

Your branches should follow one of the following patterns:

  • Core Branches:

    • main
    • master
    • develop

  • Feature, Bugfix, and Hotfix Branches:

    • feature/branch-name
    • bugfix/branch-name
    • hotfix/branch-name

  • Release Branches:

    • release/branch-name
    • Release branches may include dots (e.g., release/v1.2.0)

The tool uses a refined regular expression to ensure that only the proper characters and structure are allowed for each branch type.

Issues and Contributing

If you encounter a bug or want to see something added/changed, please go ahead and open an issue ! If you need help with something, feel free to start a discussion!

License

This project is licensed under the MIT License.

Contact

For support or any questions, please open an issue in the GitHub repository or contact [email protected].