Notary record

pypi:python-binance@1.0.37

PyPI · checked 21 Oct 2026, 22:59 UTC · checker 2026-10-19.2 · log index 876

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:59 UTC · pypi:python-binance@1.0.37

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.

Check another package

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:python-binance 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

22 of 22 installed, as npm would on linux x64 musl.

Show all 22
  • requests==2.34.2
  • six==1.17.0
  • dateparser==1.4.3
  • aiohttp==3.14.5
  • websockets==17.3
  • pycryptodome==4.1.0
  • charset-normalizer==3.5.2
  • idna==3.20
  • urllib3==2.8.0
  • certifi==2026.10.19
  • python-dateutil==2.9.0.post0
  • pytz==2026.5
  • regex==2026.9.29
  • tzlocal==5.4.4
  • aiohappyeyeballs==2.7.1
  • aiosignal==1.4.0
  • attrs==26.1.0
  • frozenlist==1.8.0
  • multidict==7.1.0
  • propcache==0.5.4
  • typing-extensions==4.16.0
  • yarl==1.25.1

Since the previous version

No comparison with an earlier version was made for this check.

Sandbox

Decoys not recordedStand-in networkTracer ebpf

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:59:54Z
contentSha256
98c4ea25ca7a684c647e0dbc962eb234e0301bf23062f3d40e43e0c649623449
contentSizeBytes
149306 (146 KB)
outputSha256
4263dc464a766fad98f9439391272be356e081e6db181020aaee4f8e1e4c9c87
log index
876

Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 22:59 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.