pypi:flask-smorest@0.47.0
PyPI · checked 21 Oct 2026, 21:07 UTC · checker 2026-10-19.2 · log index 471
Record issued 21 Oct 2026
Issued 21 Oct 2026, 21:07 UTC · pypi:flask-smorest@0.47.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:flask-smorest 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
11 of 11 installed, as npm would on linux x64 musl.
Show all 11
- werkzeug==3.1.9
- flask==3.1.3
- marshmallow==4.3.1
- webargs==8.7.1
- apispec==6.10.0
- markupsafe==3.0.4
- blinker==1.9.0
- click==8.5.0
- itsdangerous==2.2.0
- jinja2==3.1.6
- packaging==26.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-21T21:07:57Z
- contentSha256
- 9329d8697f8710ea6446e9b7876a4f58af2dbc02116d10ebac6f24a7c0ebdea9
- contentSizeBytes
- 32379 (32 KB)
- outputSha256
- 05c4f696e9f6fdc5ffa35fae51642923d5db2e116e05258cf285e957ae3494c5
- log index
- 471
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 21:07 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.