pypi:celery@5.6.3
PyPI · checked 21 Oct 2026, 22:32 UTC · checker 2026-10-19.2 · log index 774
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:32 UTC · pypi:celery@5.6.3
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:celery 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
16 of 16 installed, as npm would on linux x64 musl.
Show all 16
- billiard==4.3.1
- kombu==5.6.2
- vine==5.1.0
- click==8.5.0
- click-didyoumean==0.3.1
- click-repl==0.4.1
- click-plugins==1.1.1.2
- python-dateutil==2.9.0.post0
- tzlocal==5.4.4
- amqp==5.4.1
- tzdata==2026.5
- packaging==26.3
- prompt-toolkit==3.0.53
- typing-extensions==4.16.0
- six==1.17.0
- wcwidth==0.9.3
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-21T22:32:53Z
- contentSha256
- 0808f42f80909c4d5833202360ffafb2a4f83f4d8e23e1285d926610e9a7afa6
- contentSizeBytes
- 451235 (441 KB)
- outputSha256
- 9a475d00d28a934cf4116d50f647b9255bd868cb4f843080d54e4efc7d3b4e19
- log index
- 774
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:32 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.