habemus-papadum-mitm
Import: pdum.mitm. CLI: pdum-mitm.
Generic asyncio-managed mitmproxy sidecar with scoped CA/proxy configuration, HTTP(S)/WebSocket capture, runtime recording controls, complete JSONL payloads, processor hooks and a mountable Typer CLI. It has no Codex/model knowledge.
from pathlib import Path
from pdum.mitm import SidecarConfig, open_sidecar
async def inspect_network() -> None:
async with open_sidecar(SidecarConfig(capture_dir=Path("artifacts/captures"))) as proxy:
environment = proxy.connection.environment({}, trust="openssl")
print(proxy.connection.proxy_url)
await proxy.configure_capture(True)
print(await proxy.status())
Supply the returned environment to your consumer and keep it inside the context;
stop the consumer before closing the sidecar. Environment construction never
changes the parent process or installs a global CA. trust="node" and
trust="requests" select other explicit trust conventions.
Recording starts off. When enabled, files live under a unique run directory with
records.jsonl and manifest.json. Capture failures are observable and do not
deliberately block forwarding. There are no initial payload/run quotas. Monitor
storage and backlog; captures may contain secrets and must not be committed.
ProcessorSpec("module:factory", config={...}) selects an importable observer.
pdum.mitm.cli.create_app() returns a fresh Typer app for mounting beneath your
own command tree. Installed providers are not automatically activated.
Real local HTTP/TLS/WSS tests validate this first implementation. HTTP/2/IPv6, semantic SSE decoding, destination switching and archive rotation are not yet qualified/implemented. See current capabilities and testing rather than treating the full architecture as available behavior.
From the repository root:
./scripts/setup.sh
uv run --frozen pytest packages/mitm/tests
uv run pdum-mitm --help
uv build --package habemus-papadum-mitm
Follow AGENTS.md
and the development guide.
pdum is a shared PEP 420 namespace; do not add src/pdum/__init__.py.
Metadata
Release files for habemus-papadum-mitm 0.1.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 |
|---|---|---|---|---|
| habemus_papadum_mitm-0.1.0.tar.gz | 18.2 kB | Without provenance | Details for habemus_papadum_mitm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| habemus_papadum_mitm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for habemus_papadum_mitm-0.1.0-py3-none-any.whl |
Total release size: 36.2 kB
Release files / habemus_papadum_mitm-0.1.0.tar.gz
| Download URL | habemus_papadum_mitm-0.1.0.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
676bbcae67bb2f9e213bb4b7c962bbe625ffcac977448f93bc1958e10f76ccae
|
|
BLAKE2b-256 checksum How to use checksums |
1e11181db2a75e2b51956374a64837fc80e6c5463f35c4cad9a3ad7c6f366df6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / habemus_papadum_mitm-0.1.0-py3-none-any.whl
| Download URL | habemus_papadum_mitm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bec3ccac90801f2aceb15241aa1c89df3e4727638631ff5ea0425ac798eca61e
|
|
BLAKE2b-256 checksum How to use checksums |
78fd1fc8feaba3a8401ec6a727c4dbe9b768d4056c17201e859d6567211a7d0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for habemus-papadum-mitm 0.1.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.