pypi:dagster@1.13.25
PyPI · checked 21 Oct 2026, 20:18 UTC · checker 2026-10-19.2 · log index 279
Record issued 21 Oct 2026
Issued 21 Oct 2026, 20:18 UTC · pypi:dagster@1.13.25
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:dagster 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.
- Looked for
- file
First import
No first import was recorded for this check.
Dependencies
46 of 46 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- watchdog<7,>=0.8.3 (no wheel for this sandbox)
Show all 46
- alembic==1.20.0
- antlr4-python3-runtime==4.13.2
- click==8.5.0
- coloredlogs==14.0
- dagster-pipes==1.13.25
- dagster-shared==1.13.25
- docstring-parser==0.18.0
- filelock==4.2.4
- grpcio-health-checking==1.81.1
- grpcio==1.84.0
- jinja2==3.1.6
- protobuf==6.33.6
- python-dotenv==1.2.4
- pytz==2026.5
- requests==2.34.2
- rich==15.0.0
- six==1.17.0
- sqlalchemy==2.1.6
- structlog==26.1.0
- tabulate==0.10.0
- tomli==2.5.0
- toposort==1.10
- tqdm==4.70.1
- tzdata==2026.5
- universal-pathlib==0.3.10
- mako==1.4.3
- typing-extensions==4.16.0
- humanfriendly==10.0
- packaging==26.3
- platformdirs==4.13.5
- pydantic==2.14.1
- pyyaml==6.0.3
- tomlkit==0.15.2
- markupsafe==3.0.4
- charset-normalizer==3.5.2
- idna==3.20
- urllib3==2.8.0
- certifi==2026.10.19
- markdown-it-py==4.2.0
- pygments==2.21.0
- fsspec==2026.9.0
- pathlib-abc==0.5.2
- annotated-types==0.8.0
- pydantic-core==2.50.1
- typing-inspection==0.4.4
- 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-21T20:18:47Z
- contentSha256
- 6bc7eb0990d23fbd1393edeab8b5c067c1162ec654bdd32f95057a86eccad5e4
- contentSizeBytes
- 2031890 (1.9 MB)
- outputSha256
- 74bb867569bbd48d15134efb1037449cca54181a9ead5d8bf1dbfc03ebac9091
- log index
- 279
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 20:18 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.