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-inspect

v0.3.4

Published

GIT Inspector

Readme

git-inspect

Git repository inspector.

Used agreements from the following links to form inspection requirements:

The inspector collects information about:

  • Commits with duplicated message
  • Commits with long title message (more than 50 symbols in first commit message row)
  • Commits with short commit messages (without commit description rows)
  • Commits that are not linked to issues
  • Linearity of history
  • Obsolete branches
  • Supporting of GitFlow scheme

Supported functionality

  • Inspection of local bare repository

Install

From repository

$ git clone [email protected]:git-semver/git-inspect.git
$ cd ./git-inspect
$ npm link
$ npm install -g

From NPM registry

$ npm install git-inspect -g

Usage

In the working tree repository the inspector collects incomplete information. Now use only in bare repository directory.

$ git clone <repository> --bare
$ cd ./<repository>

Use as CLI

Run in repository directory:

$ git-inspect

Run somewhere

$ git-inspect path-to-bare-repository

Use as API

const { Inspector, Repository, schema, version } = require('git-inspect');

const cwd = process.cwd();
const repository = new Repository(cwd);
const inspector = new Inspector(repository);
const report = async inspector.collect();

Output

Report output is available in two formats:

Example JSON output:

$ git-inspect

Result:

{
  "config": {},
  "repository": {
    "remote": [
      {
        "name": "origin",
        "url": "[email protected]/user/example.git"
      }
    ],
    "directoryPath": "path/to/repository"
  },
  "results": [
    {
      "inspector": "commit",
      "reducer": "duplicatedMessage",
      "report": [
        ["4a41b496fe20a5fbea5e155999c79523536116ca"]
      ],
    },
    {
      "inspector": "commit",
      "reducer": "unlinkedTracker",
      "report": ["4a41b496fe20a5fbea5e155999c79523536116ca"],
    },
    {
      "inspector": "commit",
      "reducer": "longTitle",
      "report": ["4a41b496fe20a5fbea5e155999c79523536116ca"],
    },
    {
      "inspector": "commit",
      "reducer": "shortMessage",
      "report": ["4a41b496fe20a5fbea5e155999c79523536116ca"],
    },
    {
      "inspector": "branch",
      "reducer": "gitflow",
      "report": {
          "master": true,
          "develop": true,
          "features": true,
          "hotfixes": true,
          "releases": true,
          "other": true
        },
        "scheme": true
      },
    },
    {
      "inspector": "branch",
      "reducer": "linear",
      "report": {
        "branches": [{
          "name": "master",
          "cousins": [],
          "linearFactor": 1
        }],
        "linearFactor": 1  
      },
    },
    {
      "inspector": "branch",
      "reducer": "obsolete",
      "report": {
        "branches": [{
          "name": "feature/obsolete-feature-branch"
         }]
      },
    }
  ],
  "startTimestamp": '0000-00-00T00:00:00',
  "endTimestamp": '0000-00-00T00:00:00',
  "time": 0
}

Tests

Coverage includes integration tests and unit tests.

For run all tests, execute:

$ npm test

To run only unit tests, execute:

$ npm run test:unit

Unit tests are located next to the code. And have file mask *_test.js.

To run only integration tests, execute:

$ npm run test:integration

Integration tests are located in directory ./integration. And have file mask *_test.js.

Build with

  • NodeGit - Use for work with git repository

Feedback

TODO

See TODO LIST

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

License

This project is licensed under the GNU AGPLv3 License - see the LICENSE file for details.