Git Truck allows you to get an understanding of how your repository is structured, where there has been the most activity at different points in time, and who worked on which parts of the codebase.
.git folder🔒 Git Truck analyzes your project history using the local .git folder. It runs completely locally, so your code stays on your machine and is never uploaded to the cloud.
For each file in your repository, Git Truck lets you map metrics onto it:
You can mix and match these metrics to answer different questions about your project. The examples below show a few questions Git Truck can help your team explore.

Example from npmx.dev, a feature-rich alternative to npmjs.com.

Example from Supabase, an open source Firebase alternative.

Example from Pandas

Example from npmx.dev, a feature-rich alternative to npmjs.com.

Example from V8
In this example, we can see that during the selected time interval, the selected contributors mostly worked in isolated areas of the codebase. For example, Maja contributed prominently to the teacher folder. There is also some overlap, such as in i18n, which makes sense because internationalization is a cross-cutting concern.

Example from zeeguu/web
The only requirements are:
To run Git Truck, navigate to a repository, or a folder containing multiple repositories, and run npx git-truck. This will run the latest version of Git Truck without installing it globally.
To install the latest version of Git Truck globally, run npm install -g git-truck@latest. You can then run Git Truck from any repository using:
git truck
To update it later, run:
npm install -g git-truck@latest