pypi:pwntools@4.15.0
PyPI · checked 21 Oct 2026, 22:17 UTC · checker 2026-10-19.2 · log index 718
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:17 UTC · pypi:pwntools@4.15.0
unfinished
The check could not finish. This is not a pass.
The check could not finish (danger_pattern), so this is not a pass.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
An unfinished check is not a pass. Nothing here says the package is quiet.
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:pwntools 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.
- Looked for
- file
First import
No first import was recorded for this check.
Dependencies
34 of 34 installed, as npm would on linux x64 musl.
Show all 34
- paramiko==5.1.0
- mako==1.4.3
- pyelftools==0.33
- capstone==6.0.0a11
- ropgadget==7.7
- pyserial==3.5
- requests==2.34.2
- pip==26.2.2
- pygments==2.21.0
- pysocks==1.7.1
- python-dateutil==2.9.0.post0
- packaging==26.3
- psutil==7.2.2
- intervaltree==3.2.1
- sortedcontainers==2.4.0
- unicorn==2.1.2
- six==1.17.0
- rpyc==6.0.2
- colored-traceback==0.4.2
- unix-ar==0.2.1
- zstandard==0.25.0
- bcrypt==5.0.0
- cryptography==50.0.2
- invoke==3.0.3
- pynacl==1.6.2
- markupsafe==3.0.4
- charset-normalizer==3.5.2
- idna==3.20
- urllib3==2.8.0
- certifi==2026.10.19
- plumbum==2.0.2
- cffi==2.1.1
- typing-extensions==4.16.0
- pycparser==3.11
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
- unfinished
- verdict
- manual_review
- reasonCode
- danger_pattern
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T22:17:10Z
- contentSha256
- f5508729b310ef1e959ad324306a0964cb6f2b04a34247484e446f0343eefc5c
- contentSizeBytes
- 12873439 (12.3 MB)
- outputSha256
- e5684118c5cbb92274ac93b8557e1833baee437ac1f1827b12967a76420add3f
- log index
- 718
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:17 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.