pypi:freqtrade@2026.9
PyPI · checked 21 Oct 2026, 23:19 UTC · checker 2026-10-19.2 · log index 952
Record issued 21 Oct 2026
Issued 21 Oct 2026, 23:19 UTC · pypi:freqtrade@2026.9
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:freqtrade 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
80 of 80 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- sdnotify (no wheel for this sandbox)
Show all 80
- ccxt==4.5.89
- sqlalchemy==2.1.6
- python-telegram-bot==22.8
- humanize==4.16.0
- cachetools==7.2.4
- requests==2.34.2
- httpx==0.28.1
- urllib3==2.8.0
- certifi==2026.10.19
- jsonschema==4.26.0
- scipy==1.18.1
- numpy==2.5.4
- pandas==3.0.6
- bottleneck==1.6.0
- numexpr==2.14.2
- ta-lib==0.8.2
- ft-pandas-ta==0.3.16
- technical==1.7.0
- tabulate==0.10.0
- pycoingecko==3.2.0
- python-rapidjson==1.25
- orjson==3.13.0
- jinja2==3.1.6
- questionary==2.1.1
- prompt-toolkit==3.0.53
- joblib==1.6.0
- cloudpickle==3.1.2
- rich==15.0.0
- pyarrow==26.0.0
- fastapi==0.159.1
- pydantic==2.14.1
- pyjwt==2.15.1
- websockets==17.3
- uvicorn==0.54.0
- psutil==7.2.2
- schedule==1.2.2
- janus==2.0.0
- ast-comments==1.3.0
- aiofiles==25.1.0
- aiohttp==3.14.5
- cryptography==50.0.2
- python-dateutil==2.9.0.post0
- pytz==2026.5
- packaging==26.3
- freqtrade-client==2026.9
- typing-extensions==4.16.0
- yarl==1.25.1
- aiohttp-fast-zlib==0.3.0
- zlib-ng==1.0.0
- uvloop==0.22.1
- coincurve==21.0.0
- aiohappyeyeballs==2.7.1
- aiosignal==1.4.0
- attrs==26.1.0
- frozenlist==1.8.0
- multidict==6.9.1
- propcache==0.5.2
- cffi==2.0.0
- pycparser==3.0
- charset-normalizer==3.4.7
- idna==3.18
- anyio==4.15.1
- httpcore==1.0.9
- jsonschema-specifications==2025.9.1
- referencing==0.37.0
- rpds-py==2026.9.1
- markupsafe==3.0.4
- wcwidth==0.9.3
- markdown-it-py==4.2.0
- pygments==2.21.0
- starlette==1.9.0
- typing-inspection==0.4.4
- annotated-doc==0.0.5
- opentelemetry-api==1.45.1
- annotated-types==0.8.0
- pydantic-core==2.50.1
- click==8.5.0
- h11==0.16.0
- six==1.17.0
- mdurl==0.1.2
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-21T23:19:14Z
- contentSha256
- 3cc4432381b83ec35000bff6b76f494fa3ec7d1681c7a45c04667dc063789fac
- contentSizeBytes
- 892074 (871 KB)
- outputSha256
- b89e4d5fdc7e94d8f4a327b5feee688a4195fb902d2679028d641f54b9377233
- log index
- 952
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 23: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.