pypi:pdfplumber@0.11.10
PyPI · checked 21 Oct 2026, 22:31 UTC · checker 2026-10-19.2 · log index 770
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:31 UTC · pypi:pdfplumber@0.11.10
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:pdfplumber 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
6 of 6 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- pypdfium2>=5.9.0 (no wheel for this sandbox)
Show all 6
- pdfminer-six==20260107
- pillow==13.0.0
- charset-normalizer==3.5.2
- cryptography==50.0.2
- cffi==2.1.1
- 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
- quiet
- verdict
- approved
- reasonCode
- ran_ok
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T22:31:52Z
- contentSha256
- 7741ea81bf165b474b153e6789d10d18e06b6ddcf3ec84289c3ef2fed6802580
- contentSizeBytes
- 60047 (59 KB)
- outputSha256
- f7ec5b50f95361e659a5d0569081da99b7afe55b4296237d0bf0c039255d8009
- log index
- 770
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:31 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.