pup-down: Reports Repo Infrastructure Changes That Belong in Templates
Report-only. Compares the active repository's infrastructure against canonical templates and lists the files the repo has moved ahead on that may be worth copying back upstream.
Purpose
Professional Python repositories commonly share infrastructure such as:
- editor and Git configuration
- ignore and line-ending rules
- Markdown, YAML, and link checking
- formatting, linting, type checking, and testing
- documentation tooling
- continuous integration
- package and release validation
pup-down makes it easy to identify infrastructure improvements made
during recent work that should possibly be copied back to the canonical
templates.
Benefits
pup-down is report-only.
Each repository fetches the current baseline and compares it with its
own infrastructure.
Nothing reaches in from a central place, so:
Repo owner is in control. Run it when you choose. No files are updated. A list of changes to possibly copy to the canonical template files is provided.
Templates are fetched by immutable commit SHA, so an update always reflects the latest push to the template repository and every run is pinned to an exact template commit.
Repo type is inferred from the presence of key files so no extensive configuration is needed. For example:
- ALL REPOS
pyproject.tomlindicates ALL PY REPOSpyproject.toml+srcindicates ALL PY SRC REPOS
Default Template Source
Compare a Repo with Templates
# compare with canonical templates
uvx pup-down@latest
# compare using the latest published pup-down version
uvx pup-down@latest
Developer Command Reference
Show command reference
In a machine terminal
Open a machine terminal where you want the project:
git clone https://github.com/pup-pack/pup-down
cd pup-down
code .
In a VS Code terminal
uv self update
uv python pin 3.15
uv python install
uv lock --upgrade
uv sync
uv run pre-commit install
uv run pre-commit autoupdate
git add -A
uv run pre-commit run --all-files
# repeat if changes were made
uv run pre-commit run --all-files
# run locally to test
uv run pup-down
# types, tests, docs
uv run ty check
uv run python -m pytest
uv run python -m zensical build
# save progress
git add -A
git commit -m "update"
git push -u origin main
Documentation
Annotations
Citation
License
Metadata
Release files for pup-down 0.2.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 | |
|---|---|---|---|
| pup_down-0.2.0.tar.gz | 11.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pup_down-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.8 kB
Release files / pup_down-0.2.0.tar.gz
| Download URL | pup_down-0.2.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8aa2c3cd8ab60ff86ff5a9bd47f18851013867115eb6772cd74682f53b655afb
|
|
BLAKE2b-256 checksum How to use checksums |
fe5c7c61f997094790ba709a2ebb5d74e3e6838f0eba3389a95c5d113fa61b44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency logRelease files / pup_down-0.2.0-py3-none-any.whl
| Download URL | pup_down-0.2.0-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1b571dd54fde3215ecfe466cfb441571e4a1768846e00f9ed74290d960730b0
|
|
BLAKE2b-256 checksum How to use checksums |
5ffc0fca1a02939faf2c778cb603f631360773321824bf5b162c68823067a8ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency log