pypi:taskiq@0.13.0
PyPI · checked 21 Oct 2026, 20:33 UTC · checker 2026-10-19.2 · log index 338
Record issued 21 Oct 2026
Issued 21 Oct 2026, 20:33 UTC · pypi:taskiq@0.13.0
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:taskiq 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
17 of 17 installed, as npm would on linux x64 musl.
Show all 17
- aiohttp==3.14.5
- anyio==4.15.1
- pycron==3.3.0
- pydantic==2.14.1
- taskiq-dependencies==1.5.7
- 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
- idna==3.20
- annotated-types==0.8.0
- pydantic-core==2.50.1
- typing-inspection==0.4.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
- quiet
- verdict
- approved
- reasonCode
- ran_ok
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T20:33:27Z
- contentSha256
- b51e1961d8919bc897caa6f5484ac08d812341413a20a3704b69c597c4c154d2
- contentSizeBytes
- 94856 (93 KB)
- outputSha256
- d0bef5c5ec0f3f5a2587f5313feae08bc79d36eeacc013d7c403ecb2333e6852
- log index
- 338
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 20:33 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.