🧳 pybundle 
Why pybundle?
pybundle exists to solve a boring but expensive problem:
Context loss.
Modern debugging, CI, audits, and AI-assisted workflows fail not because tools are weak — but because context is fragmented, ephemeral, or missing entirely.
pybundle creates a single, deterministic artifact that captures:
- the exact source code that mattered
- the tools that ran (and their versions)
- the environment they ran in
- the outputs they produced
- and the metadata required to reproduce or reason about it later
For humans, automation, and AI.
Think:
git archive+ diagnostics + metadata without heuristics, guesswork, or “works on my machine.”
What pybundle is good at
pybundle is designed for:
- handing a project to another engineer
- attaching full context to a bug report
- generating CI artifacts that actually explain failures
- feeding codebases to AI tools without noise
- audits, reviews, and reproducibility
- answering “what exactly did we run?” weeks later
It prioritizes determinism, traceability, and automation over cleverness.
Installation
pip install gwc-pybundle
Note: The PyPI package name is
gwc-pybundle, but the CLI command ispybundle.
Quick sanity check:
pybundle version
Where to go next
📚 Documentation (Wiki) ➡ https://github.com/girls-whocode/pybundle/wiki
The Wiki contains:
- Usage and profiles
- Security & redaction
- JSON output contracts
- CI integration
- AI handoff workflows
- FAQs and design rationale
💬 Questions & Discussion ➡ https://github.com/girls-whocode/pybundle/discussions
Use Discussions for:
- “Is pybundle right for this?”
- Workflow questions
- Design feedback
- Feature ideas
- Real-world use cases
Philosophy
If a tool produces output, it should also produce metadata explaining how and why that output exists.
pybundle treats context as a first-class artifact.
License
MIT License
1 maintainer
Release files for gwc-pybundle 2.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gwc_pybundle-2.2.1.tar.gz | 124.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gwc_pybundle-2.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 297.4 kB
Release files / gwc_pybundle-2.2.1.tar.gz
| Download URL | gwc_pybundle-2.2.1.tar.gz |
|---|---|
| Size | 124.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bd3da9796ff6a5af7708bac393907c44168cff8974e21aa06ea6684b487b0e1
|
|
BLAKE2b-256 checksum How to use checksums |
0591fbaa2802bde47aada9c657aaba29dc961f2852050a06c03fea3078545223
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency logRelease files / gwc_pybundle-2.2.1-py3-none-any.whl
| Download URL | gwc_pybundle-2.2.1-py3-none-any.whl |
|---|---|
| Size | 173.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39a3117d8ab6d9da874eb1cb186f1015ba0555c5e45f3e5f3d8fe19987ce875d
|
|
BLAKE2b-256 checksum How to use checksums |
0fdea7114dfbef829e6705c6f54b1f4af101ac73ced2809c29b70a606a02c6a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency log
