pypi:pyfolio-reloaded@0.9.9
PyPI · checked 21 Oct 2026, 21:27 UTC · checker 2026-10-19.2 · log index 539
Record issued 21 Oct 2026
Issued 21 Oct 2026, 21:27 UTC · pypi:pyfolio-reloaded@0.9.9
unfinished
The check could not finish. This is not a pass.
The check could not finish (import_failed), 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:pyfolio-reloaded 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
- fc-list
First import
No first import was recorded for this check.
Dependencies
34 of 34 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- peewee<3.17.4 (no wheel for this sandbox)
- scikit-learn>=0.16.1 (no wheel for this sandbox)
Show all 34
- numpy==2.5.4
- pandas==2.3.3
- ipython==9.17.1
- matplotlib==3.11.2
- pytz==2026.5
- scipy==1.18.1
- seaborn==0.13.2
- empyrical-reloaded==0.7.0
- python-dateutil==2.9.0.post0
- tzdata==2026.5
- ipython-pygments-lexers==1.1.1
- jedi==0.20.1
- matplotlib-inline==0.2.2
- pexpect==4.9.0
- prompt-toolkit==3.0.53
- psutil==7.2.2
- pygments==2.21.0
- stack-data==0.6.3
- traitlets==5.16.1
- contourpy==1.4.0
- cycler==0.12.1
- fonttools==4.67.0
- kiwisolver==1.5.1
- packaging==26.3
- pillow==13.0.0
- pyparsing==3.3.3
- bottleneck==1.6.0
- 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
- import_failed
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T21:27:16Z
- contentSha256
- aa0e136b379bc6c7a48a74746c784c263de986575af5377348330eb1aed8791c
- contentSizeBytes
- 6221185 (5.9 MB)
- outputSha256
- da87f254ea80c04185b2111f84a11c8769850565ca426205e63236f60fb07920
- log index
- 539
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 21:27 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.