pypi:pymc@6.3.2
PyPI · checked 21 Oct 2026, 20:59 UTC · checker 2026-10-19.2 · log index 436
Record issued 21 Oct 2026
Issued 21 Oct 2026, 20:59 UTC · pypi:pymc@6.3.2
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:pymc 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
- g++
First import
No first import was recorded for this check.
Dependencies
24 of 24 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- numba<=0.68.0,>=0.58 (no wheel for this sandbox)
Show all 24
- arviz==1.3.0
- cachetools==6.2.6
- cloudpickle==3.1.2
- numpy==2.5.4
- pandas==3.0.6
- pytensor==3.3.4
- rich==15.0.0
- scipy==1.18.1
- threadpoolctl==3.7.0
- typing-extensions==4.16.0
- arviz-base==1.3.1
- arviz-stats==1.3.3
- arviz-plots==1.3.2
- python-dateutil==2.9.0.post0
- setuptools==84.2.1
- filelock==4.2.4
- markdown-it-py==4.2.0
- pygments==2.21.0
- xarray==2026.9.0
- lazy-loader==0.6
- xarray-einstats==0.11.0
- six==1.17.0
- mdurl==0.1.2
- 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-21T20:59:12Z
- contentSha256
- f3eef7d1637d4bac243562abcd087a5363e99103ae984c69ab72d081f2eb0a1e
- contentSizeBytes
- 608275 (594 KB)
- outputSha256
- 581eb19859fe1660d771a8d3b4a15c9efe0b804399c116cd0f2ccb2f7e144ba2
- log index
- 436
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 20:59 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.