pypi:chalice@1.33.0
PyPI · checked 21 Oct 2026, 22:00 UTC · checker 2026-10-19.2 · log index 661
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:00 UTC · pypi:chalice@1.33.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:chalice 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
19 of 19 installed, as npm would on linux x64 musl.
Show all 19
- click==8.5.0
- botocore==1.43.117
- six==1.17.0
- pip==26.1.2
- jmespath==1.1.0
- pyyaml==6.0.3
- inquirer==3.4.1
- wheel==0.48.0
- setuptools==84.2.1
- python-dateutil==2.9.0.post0
- urllib3==2.8.0
- blessed==1.52.0
- editor==2.0.1
- readchar==4.2.2
- packaging==26.3
- wcwidth==0.9.3
- jinxed==2.1.0
- runs==1.3.0
- xmod==1.10.0
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:00:33Z
- contentSha256
- b7748cac1e23633c3e72e6de5a17a90627dd0335cc3166ef7fc7043b6d4792ca
- contentSizeBytes
- 265872 (260 KB)
- outputSha256
- de474d22f229da28a4cee752cd531aee798417db7f35b30a606b8c680a70ce4b
- log index
- 661
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:00 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.