pypi:litestar@2.24.0
PyPI · checked 21 Oct 2026, 22:51 UTC · checker 2026-10-19.2 · log index 845
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:51 UTC · pypi:litestar@2.24.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:litestar 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
21 of 21 installed, as npm would on linux x64 musl.
Show all 21
- anyio==4.15.1
- click==8.5.0
- httpx==0.28.1
- litestar-htmx==0.5.0
- msgspec==0.22.0
- multidict==7.1.0
- multipart==2.0.1
- polyfactory==3.5.0
- pyyaml==6.0.3
- rich-click==1.9.9
- rich==15.0.0
- sniffio==1.3.1
- typing-extensions==4.16.0
- idna==3.20
- certifi==2026.10.19
- httpcore==1.0.9
- faker==40.43.0
- markdown-it-py==4.2.0
- pygments==2.21.0
- h11==0.16.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-21T22:51:37Z
- contentSha256
- 0ef13630173ea147847363f03f0459877ab14a572e68b2af7a25796055513a31
- contentSizeBytes
- 581807 (568 KB)
- outputSha256
- 84db433286cc64144d9d2a177babe1415999036d5f4a7c76536be4cb518d997d
- log index
- 845
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:51 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.