pypi:voila@0.5.13
PyPI · checked 21 Oct 2026, 22:19 UTC · checker 2026-10-19.2 · log index 726
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:19 UTC · pypi:voila@0.5.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:voila 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
57 of 57 installed, as npm would on linux x64 musl.
Show all 57
- jupyter-client==8.10.0
- jupyter-core==5.9.1
- jupyter-server==2.21.1
- jupyterlab-server==2.28.1
- nbclient==0.11.0
- nbconvert==7.17.2
- traitlets==5.16.1
- websockets==17.3
- python-dateutil==2.9.0.post0
- pyzmq==27.2.0
- tornado==6.6
- typing-extensions==4.16.0
- platformdirs==4.13.5
- anyio==4.15.1
- argon2-cffi==25.1.0
- jinja2==3.1.6
- jupyter-events==0.12.1
- jupyter-server-terminals==0.5.4
- nbformat==5.11.1
- packaging==26.3
- prometheus-client==0.26.0
- send2trash==2.1.0
- terminado==0.18.1
- websocket-client==1.9.2
- babel==2.18.0
- json5==0.17.3
- jsonschema==4.26.0
- requests==2.34.2
- beautifulsoup4==4.15.0
- bleach==6.4.0
- defusedxml==0.7.1
- jupyterlab-pygments==0.3.0
- markupsafe==3.0.4
- mistune==3.4.0
- pandocfilters==1.5.1
- pygments==2.21.0
- six==1.17.0
- idna==3.20
- argon2-cffi-bindings==26.1.0
- python-json-logger==4.2.0
- pyyaml==6.0.3
- referencing==0.37.0
- rfc3339-validator==0.1.4
- rfc3986-validator==0.1.1
- fastjsonschema==2.22.2
- ptyprocess==0.7.0
- attrs==26.1.0
- jsonschema-specifications==2025.9.1
- rpds-py==2026.9.1
- charset-normalizer==3.5.2
- urllib3==2.8.0
- certifi==2026.10.19
- soupsieve==3.0.3
- webencodings==0.6.1
- tinycss2==1.5.1
- 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:19:31Z
- contentSha256
- 75dc515f0f814182088317923c2f15d22a5355766bb5eb04ae2370ce2e2f3652
- contentSizeBytes
- 4563905 (4.4 MB)
- outputSha256
- 7d2087e1f098e16fd903d2e046e7147bcf47e4bcbfa2a4aaafaef4190ba10442
- log index
- 726
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:19 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.