gitplot
Git history visualizations from the command line.
Quick Start
uvx gitplot sediment https://github.com/pola-rs/polars
uvx gitplot sediment /path/to/local/repo --samples 50 --workers 2
Charts
sediment
Stacked area chart showing code age layers over time. Each color band represents lines of code from a specific time period, revealing how quickly code gets replaced.
Based on gitcharts by Vincent D. Warmerdam.
gitplot sediment repo # default: quarter granularity, 100 samples, PNG
gitplot sediment repo --granularity year # group by year instead of quarter
gitplot sediment repo --since 2023-01-01 # only show recent history
gitplot sediment repo --format svg # SVG output
gitplot sediment repo --samples 200 # more data points (incremental)
gitplot sediment repo --include '\.py$' # only Python files
gitplot sediment repo --exclude 'tests/|lock' # drop tests and lockfiles
open $(gitplot sediment repo --quiet) # open the chart directly
--include/--exclude are regexes matched against each file's path; they also
work on survivors and busfactor. By default every tracked file is analyzed.
Raw blame data is stored as parquet for incremental reuse. Re-running with more
samples only computes the delta. Changing visual settings (granularity, since,
format) is instant; changing --include/--exclude re-collects, since they
determine which files get blamed.
Development
uv sync
make check
make test
Metadata
Release files for gitplot 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gitplot-0.3.0.tar.gz | 10.3 kB | Without provenance | Details for gitplot-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitplot-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for gitplot-0.3.0-py3-none-any.whl |
Total release size: 27.6 kB
Release files / gitplot-0.3.0.tar.gz
| Download URL | gitplot-0.3.0.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aae2b65e07d17c522144c11c10160df269b2a009cc97d5af5fcd605a432fc8a5
|
|
BLAKE2b-256 checksum How to use checksums |
e80360c72610139c6d5b9936bb1b82f17c8f929ebeebcebf4df7f73e4366136e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.17 {"installer":{"name":"uv","version":"0.11.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / gitplot-0.3.0-py3-none-any.whl
| Download URL | gitplot-0.3.0-py3-none-any.whl |
|---|---|
| Size | 17.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb4b397aa4b4f71faa106c3199cd7fb0a83dd09a07f086360cdd452bb95524e5
|
|
BLAKE2b-256 checksum How to use checksums |
882ed490d9cf2acf84dd468bba7caddc5c03fc1dbf446643a50685a5f82f55ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.17 {"installer":{"name":"uv","version":"0.11.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for gitplot 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.