pypi:ipdb@0.13.13
PyPI · checked 21 Oct 2026, 21:41 UTC · checker 2026-10-19.2 · log index 598
Record issued 21 Oct 2026
Issued 21 Oct 2026, 21:41 UTC · pypi:ipdb@0.13.13
quiet
Its install steps ran with decoy credentials in reach and touched nothing we watch.
It ran here and reached for nothing on the network. That is evidence, not proof: code can wait for a different machine.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
Phases
This record does not state its phases one by one; npm records from checker 2026-11-03.1 and Python records from 2026-11-04.3 on do.
Install steps
pypi:ipdb has no install step of its own.
No dependency runs anything at install.
What the run reached
No install step reached anything we watch.
- Programs
- python3
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
First import
No first import was recorded for this check.
Dependencies
17 of 17 installed, as npm would on linux x64 musl.
Show all 17
- ipython==9.17.1
- decorator==5.3.1
- ipython-pygments-lexers==1.1.1
- jedi==0.20.1
- matplotlib-inline==0.2.2
- pexpect==4.9.0
- prompt-toolkit==3.0.53
- psutil==7.2.2
- pygments==2.21.0
- stack-data==0.6.3
- traitlets==5.16.1
- parso==0.8.7
- ptyprocess==0.7.0
- wcwidth==0.9.3
- executing==2.3.0
- asttokens==3.0.2
- pure-eval==0.2.4
Since the previous version
No comparison with an earlier version was made for this check.
Sandbox
network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user
Signature and transparency log
- level
- quiet
- verdict
- approved
- reasonCode
- ran_ok
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T21:41:56Z
- contentSha256
- 45529994741c4ab6d2388bfa5d7b725c2cf7fe9deffabdb8a6113aa5ed449ed4
- contentSizeBytes
- 12130 (12 KB)
- outputSha256
- 4fca3c6da6be497f5a6669c3dd632ef94ea81cbcd5f11914f89983969b24cf35
- log index
- 598
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 21:41 UTC
What this does and does not say
The claim is about the bytes, not the name.
The signature covers these exact bytes. Another version is another check.
A quiet trace is evidence, not proof.
Code that only runs later, when your app calls it, is out of reach.
A signature is not an endorsement.
It says what happened, not that the code is good.
Twenty checks an hour for each network address. When a limit is ours, the record says unfinished and names it.