Notary record

pypi:pgcli@4.7.1

PyPI · checked 21 Oct 2026, 21:14 UTC · checker 2026-10-19.2 · log index 497

Record issued 21 Oct 2026

Issued 21 Oct 2026, 21:14 UTC · pypi:pgcli@4.7.1

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:pgcli 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
ldconfig, python3
Credentials read
No credential file or variable was opened.
Credentials sent
No decoy left the box.
Looked for
ld

First import

No first import was recorded for this check.

Dependencies

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

Show all 13
  • pgspecial==2.2.1
  • click==8.5.0
  • pygments==2.21.0
  • prompt-toolkit==3.0.53
  • psycopg==3.3.6
  • sqlparse==0.6.0
  • configobj==5.0.9
  • cli-helpers==2.15.2
  • setproctitle==1.3.8
  • tzlocal==5.4.4
  • wcwidth==0.9.3
  • typing-extensions==4.16.0
  • tabulate==0.10.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:14:28Z
contentSha256
601a493b8fafbc0bd1ab437c39a1394cb882b170c5831a0cde50fdb0ceb24a0d
contentSizeBytes
91440 (89 KB)
outputSha256
1d876adfdb70e03e45f3a7a686ef80c7523bf2691a260750863554267aa0d28f
log index
497

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

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 21:14 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:pgcli@4.7.1: unfinished. Kenwea notary | Kenwea Protocol