Notary record

pypi:openai-agents@0.22.3

PyPI · checked 21 Oct 2026, 22:52 UTC · checker 2026-10-19.2 · log index 847

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:52 UTC · pypi:openai-agents@0.22.3

unfinished

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

The check could not finish (import_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:openai-agents 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

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

Show all 34
  • griffelib==2.4.0
  • httpx2==2.16.0
  • mcp==2.3.0
  • openai==3.36.0
  • pydantic==2.14.1
  • pyjwt==2.15.1
  • python-multipart==0.0.32
  • requests==2.34.2
  • starlette==1.9.0
  • typing-extensions==4.16.0
  • urllib3==2.8.0
  • websockets==16.1.1
  • anyio==4.15.1
  • httpcore2==2.16.0
  • idna==3.20
  • truststore==0.10.5
  • jsonschema==4.26.0
  • mcp-types==2.3.0
  • opentelemetry-api==1.45.1
  • sse-starlette==3.5.0
  • typing-inspection==0.4.4
  • uvicorn==0.54.0
  • jiter==0.17.0
  • sniffio==1.3.1
  • annotated-types==0.8.0
  • pydantic-core==2.50.1
  • charset-normalizer==3.5.2
  • certifi==2026.10.19
  • h11==0.16.0
  • attrs==26.1.0
  • jsonschema-specifications==2025.9.1
  • referencing==0.37.0
  • rpds-py==2026.9.1
  • click==8.5.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
import_failed
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T22:52:18Z
contentSha256
41dec9e2e703db32a627bf0290f3721a6ca37405603a8cb654213356dbb8ee9d
contentSizeBytes
1149658 (1.1 MB)
outputSha256
10bcff65e6b53cdcf8574686187cd9c96b76b8bbadd4abe5636eba5a2c7ebd21
log index
847

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

Inclusion proofCheckpointKey list

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