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-truck-beta

v0.0.41

Published

Visualizing a Git repository

Readme

Git Truck Beta

GitHub license Git Truck Beta  on NPM

Demo

Important!

It is a private version of the original version of GitTruck, you might be searching for the GitTruck base version available here

Description

Git-Truck provides you with a truckload of visualizations for your git repository, and helps you find out if your project has a good truck factor:

| | | |-|-| | The files in your system where you have a single contributor (i.e., truck-factor = 1) | | | You can see how the various developers contribute to your codebase | | | You can determine which parts of the system that are most often changed | |

What makes Git Truck Beta different?

  • Private by design
  • Works offline
  • Git provider agnostic - Works with any Git repository
  • No tracking, no ads, no data mining, no analytics, no cloud, no servers

Prerequisites

To use Git Truck Beta , you will need to have the following programs installed:

  • Node.js 16.13 or newer
  • npm 6.14 or newer
  • git 2.29 or newer

To check if these programs are installed, and what version you have, run node --version, npm --version and git --version. If any of these are not installed on your system, or are just very old, they can be installed from the links above. Note that npm is installed along with node.

Get started

  1. Within a git repository, or a directory containing git repositories, run the command npx -y git-truck.
  2. The application will now open in your default browser.

I got an error or I want to give feedback, what do i do?

Please contact Dawid Wozniak by email [email protected]

Advanced use

Run npx git-truck in the root of a git repository, that you want to visualize:

npx git-truck [args]

Arguments

| arg | description | default value | | :------------------: | :-------------------------------------------------------------------: | :----------------: | | --path | path to a folder or a git repository | current directory | | --log | output log level. See here for values | - | | --port | port to use for the program | 3000 | | --invalidate-cache | bypass analyzer cache manually | - | | --headless | run the program without opening the browser | - |

Note: Using --invalidate-cache will cause the analyzer to run every time the client talks to the server.

Configuration

You can add a truckconfig.json file to the root of your project, where you can define the arguments you want. Additionally you can define which git-aliases should be considered as the same person using unionedAuthors. If provided, the first name in the array is used as the name of the person. You can also define files to ignore.

Example:

{
  "log": "debug",
  "branch": "main",
  "unionedAuthors": [
    ["Bob", "Bobby Bob"],
    ["Alice", "aliiii", "alice alice"]
  ],
  "hiddenFiles": ["package-lock.json", "*.bin", "*.svg"],
  "invalidateCache": true
}