pypi:seleniumbase@4.55.0
PyPI · checked 21 Oct 2026, 21:07 UTC · checker 2026-10-19.2 · log index 467
Record issued 21 Oct 2026
Issued 21 Oct 2026, 21:07 UTC · pypi:seleniumbase@4.55.0
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:seleniumbase 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
57 of 57 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- pyautogui>=0.9.54 (no wheel for this sandbox)
Show all 57
- pip==26.2.2
- packaging==26.3
- setuptools==84.2.1
- wheel==0.48.0
- attrs==26.1.0
- certifi==2026.10.19
- exceptiongroup==1.3.1
- websockets==17.3
- filelock==4.2.4
- fasteners==0.20
- mycdp==1.4.0
- pynose==1.5.5
- typing-extensions==4.16.0
- sbvirtualdisplay==1.4.0
- markupsafe==3.0.4
- jinja2==3.1.6
- six==1.17.0
- parse==1.22.4
- parse-type==0.6.6
- colorama==0.4.6
- psutil==7.2.2
- pyyaml==6.0.3
- pygments==2.21.0
- tabcompleter==1.4.1
- pdbp==1.8.3
- idna==3.20
- charset-normalizer==3.5.2
- urllib3==2.8.0
- requests==2.34.2
- sniffio==1.3.1
- h11==0.16.0
- outcome==1.3.0.post0
- trio==0.34.0
- trio-websocket==0.12.2
- wsproto==1.3.2
- websocket-client==1.9.2
- selenium==4.50.0
- cssselect==1.6.0
- sortedcontainers==2.4.0
- execnet==2.1.2
- iniconfig==2.3.0
- pluggy==1.6.0
- pytest==9.1.1
- pytest-html==4.0.2
- pytest-metadata==3.1.1
- pytest-ordering==0.6
- pytest-rerunfailures==16.7
- pytest-xdist==3.8.0
- parameterized==0.9.0
- behave==1.2.6
- soupsieve==2.10
- beautifulsoup4==4.15.0
- pyotp==2.10.0
- python-xlib==0.33
- markdown-it-py==4.2.0
- mdurl==0.1.2
- rich==15.0.0
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:07:19Z
- contentSha256
- 777d52393e74a700c474aeefd9c2ea3ad17ae48b66f227f436a52dd1553f7e0f
- contentSizeBytes
- 700385 (684 KB)
- outputSha256
- 596366a09c06e66dccc6a0d67ab4a4c2c196216e30bcb0c63f7cad1bfe9c6d14
- log index
- 467
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 21:07 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.