Notary record

pypi:diffusers@0.40.0

PyPI · checked 21 Oct 2026, 21:19 UTC · checker 2026-10-19.2 · log index 508

Record issued 21 Oct 2026

Issued 21 Oct 2026, 21:19 UTC · pypi:diffusers@0.40.0

unfinished

The check could not finish. This is not a pass.

The check could not finish (entry_point_failed), so this is not a pass.

The trace shows what a step attempted. A quiet trace is evidence, not proof.

An unfinished check is not a pass. Nothing here says the package is quiet.

Check another package

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:diffusers has no install step of its own.

No dependency runs anything at install.

What the run reached

DNS
  • huggingface.co
Requests
  • TLS to huggingface.co:443 (1536 bytes sent, encrypted)
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

24 of 24 installed, as npm would on linux x64 musl.

Show all 24
  • importlib-metadata==9.0.1
  • filelock==4.2.4
  • httpx==0.28.1
  • huggingface-hub==1.33.0
  • numpy==2.5.4
  • regex==2026.9.29
  • requests==2.34.2
  • safetensors==0.8.0
  • pillow==13.0.0
  • zipp==4.1.2
  • anyio==4.15.1
  • certifi==2026.10.19
  • httpcore==1.0.9
  • idna==3.20
  • click==8.5.0
  • fsspec==2026.9.0
  • hf-xet==1.7.0
  • packaging==26.3
  • pyyaml==6.0.3
  • tqdm==4.70.1
  • typing-extensions==4.16.0
  • charset-normalizer==3.5.2
  • urllib3==2.8.0
  • h11==0.16.0

Since the previous version

No comparison with an earlier version was made for this check.

Sandbox

Decoys not recordedStand-in networkTracer ebpf

network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user

Signature and transparency log

level
unfinished
verdict
manual_review
reasonCode
entry_point_failed
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T21:19:05Z
contentSha256
5b5da7c3ddb62152fa4afc577f02e050af688c797375c34fb2d01006da3f3541
contentSizeBytes
5911654 (5.6 MB)
outputSha256
82f974ae15ef4b1bce105c9e1307e19ab4f6282ef5fcdcbd9daf32980131b618
log index
508

Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 21:19 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.

pypi:diffusers@0.40.0: unfinished. Kenwea notary | Kenwea Protocol