pypi:pygwalker@0.5.0.1
PyPI · checked 21 Oct 2026, 22:34 UTC · checker 2026-10-19.2 · log index 777
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:34 UTC · pypi:pygwalker@0.5.0.1
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:pygwalker 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
- anywidget==0.11.0
- appdirs==1.4.4
- arrow==1.4.0
- astor==0.8.1
- cachetools==7.2.4
- duckdb==1.3.2
- gw-dsl-parser==0.1.49.1
- ipylab==1.0.0
- ipython==9.17.1
- ipywidgets==8.1.9
- jinja2==3.1.6
- kanaries-track==0.0.5
- numpy==2.5.4
- packaging==26.3
- pandas==3.0.6
- psutil==7.2.2
- pyarrow==26.0.0
- pydantic==2.14.1
- pytz==2026.5
- requests==2.34.2
- segment-analytics-python==2.2.3
- sqlalchemy==2.1.6
- sqlglot==30.24.0
- traitlets==5.16.1
- typing-extensions==4.16.0
- psygnal==0.16.1
- python-dateutil==2.9.0.post0
- tzdata==2026.5
- wasmtime==49.0.0
- ipython-pygments-lexers==1.1.1
- jedi==0.20.1
- matplotlib-inline==0.2.2
- pexpect==4.9.0
- prompt-toolkit==3.0.53
- pygments==2.21.0
- stack-data==0.6.3
- comm==0.2.3
- widgetsnbextension==4.0.16
- jupyterlab-widgets==3.0.17
- markupsafe==3.0.4
- backoff==2.2.1
- dateutils==0.6.12
- annotated-types==0.8.0
- pydantic-core==2.50.1
- typing-inspection==0.4.4
- charset-normalizer==3.5.2
- idna==3.20
- urllib3==2.8.0
- certifi==2026.10.19
- monotonic==1.6
- six==1.17.0
- 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
- unfinished
- verdict
- manual_review
- reasonCode
- danger_pattern
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T22:34:24Z
- contentSha256
- 888b7959cb9132ccd6deba4a060d730f919300420f172ab3cfaa2e2e290f1315
- contentSizeBytes
- 4842139 (4.6 MB)
- outputSha256
- 078e738a4f6de3922aa3cd88dd72e51a32e75e5840e357b6648030f5a3136746
- log index
- 777
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:34 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.