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

git-semver-info

v0.5.1

Published

GitSemver Info tool

Readme

git-semver-info npm David

This library is intended for define semantic version of package by the git environment. It's inspired by GitFlow, SemVer 2.0.0, GitVersion.

Base agreements:

  • The stable versions of the package should be are announced by the developer in master branches
  • Unstable versions of the package could be auto computed by the git environment on CI server
  • Development should be carried out within the framework of the GitFlow, and package versions should be based on SemVer 2.0.0.

In order to CI server can publish the package as unstable (prerelease) and stable version. For definition to be performed correctly, it is necessary to observe GitFlow branching model.

This definition available for following branches:

  • master - package version remains as is X.Y.Z
  • develop - to package version is X.(Y+1).0-alpha.{commits}
  • feature/* - to package version is X.(Y+1).0-feature-{hash}.{commits}
  • release/vX'.Y'.Z' - to package version is X'.Y'.Z'-rc.{commits}
  • hotfix/* - to package version is X.Y.(Z+1)-beta.{commits}

X - current major version declarate in package.json

Y - current minor version declarate in package.json

Z - current patch version declarate in package.json

{hash} - it's first feature branch commit (generic commit from develop and feature branch)

{commits} - quantity commits from branch start.

Prerelease path could be override with config file git-semver-info.json. This config file should be place into current work directory.

Config file content (default value):

{
  "prerelease": {
    "develop": "alpha.${developBranchCommitsCount}",
    "feature": "feature-${firstFeatureCommitSha}.${featureBranchCommitsCount}",
    "hotfix": "beta.${hotfixBranchCommitsCount}",
    "release": "rc.${releaseBranchCommitsCount}"
  }
}

Example

The final semantic version of the package looks like:

<major>.<minor>.<patch>-<prerelease>+<build-number>

For example for branch feature/feature-long-name and package main version 1.2.3, it's prerelease version looks like:

1.2.3-feature-3kn3erb.13+42

Install

$ npm i git-semver-info -g

Usage

In package directory (where placed file package.json) run:

$ git-semver-info --help

Output:

Usage: git-semver-info [options] [cwd]


Options:

  -v, --version   output the version number
  -j, --json      output as JSON
  -t, --teamcity  output for TeamCity as service message
  -w, --write     write version into package.json
  -h, --help      output usage information