Notary record

pypi:deepgram-sdk@7.11.0

PyPI · checked 21 Oct 2026, 16:27 UTC · checker 2026-10-19.2 · log index 250

Record issued 21 Oct 2026

Issued 21 Oct 2026, 16:27 UTC · pypi:deepgram-sdk@7.11.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.

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:deepgram-sdk 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

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

Show all 12
  • httpx==0.28.1
  • pydantic==2.14.1
  • pydantic-core==2.50.1
  • typing-extensions==4.16.0
  • websockets==17.3
  • anyio==4.15.1
  • certifi==2026.10.19
  • httpcore==1.0.9
  • idna==3.20
  • annotated-types==0.8.0
  • typing-inspection==0.4.4
  • 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
quiet
verdict
approved
reasonCode
ran_ok
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T16:27:35Z
contentSha256
bc8aa74e6338a1f508829fe9ca4c628770fde136035e5895f623bad0968b18f6
contentSizeBytes
647309 (632 KB)
outputSha256
94e663eb42baf7b67a1b3fd58cb7cc4fcb69041d1022c4d2ecfb8e7d59e3959f
log index
250

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

Inclusion proofCheckpointKey list

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