Notary record

pypi:logfire@5.1.1

PyPI · checked 21 Oct 2026, 20:39 UTC · checker 2026-10-19.2 · log index 365

Record issued 21 Oct 2026

Issued 21 Oct 2026, 20:39 UTC · pypi:logfire@5.1.1

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:logfire 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

22 of 22 installed, as npm would on linux x64 musl. The tree is not complete.

Not installed:

  • opentelemetry-api==1.44.0 (wanted by opentelemetry-sdk; 1.45.1 is installed)
  • opentelemetry-semantic-conventions==0.65b0 (wanted by opentelemetry-sdk; 0.66b1 is installed)
Show all 22
  • executing==2.3.0
  • opentelemetry-exporter-otlp-proto-http==1.44.0
  • opentelemetry-instrumentation==0.66b1
  • opentelemetry-sdk==1.44.0
  • protobuf==7.36.2
  • rich==15.0.0
  • typing-extensions==4.16.0
  • googleapis-common-protos==1.75.5
  • opentelemetry-api==1.45.1
  • opentelemetry-exporter-otlp-proto-common==1.44.0
  • opentelemetry-proto==1.44.0
  • requests==2.34.2
  • opentelemetry-semantic-conventions==0.66b1
  • packaging==26.3
  • wrapt==2.5.1
  • markdown-it-py==4.2.0
  • pygments==2.21.0
  • charset-normalizer==3.5.2
  • idna==3.20
  • urllib3==2.8.0
  • certifi==2026.10.19
  • mdurl==0.1.2

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-21T20:39:56Z
contentSha256
ee2e25b83830f52ea3d7a1b35cf6f783490b2ba349f0383ca8ae6f5ff2a4f7dd
contentSizeBytes
479430 (468 KB)
outputSha256
680a75bb237afc2a33ac34679af94d6f3086196e44f1ba5613ef8b2e3b72daee
log index
365

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

Inclusion proofCheckpointKey list

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