Notary record

pypi:hatch@1.18.1

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:08 UTC · pypi:hatch@1.18.1

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

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

Not installed:

  • uv>=0.5.23 (no wheel for this sandbox)
Show all 42
  • backports-zstd==1.8.0
  • click==8.5.0
  • distro==1.9.0
  • hatchling==1.32.4
  • httpx2==2.16.0
  • hyperlink==21.0.0
  • keyring==25.7.0
  • packaging==26.3
  • pexpect==4.9.0
  • platformdirs==4.13.5
  • pyproject-hooks==1.3.3
  • python-discovery==1.6.4
  • rich==15.0.0
  • shellingham==1.5.4
  • tomli-w==1.2.0
  • tomlkit==0.15.2
  • userpath==1.9.2
  • virtualenv==21.14.12
  • pathspec==1.1.1
  • pluggy==1.7.0
  • trove-classifiers==2026.9.21.13
  • anyio==4.15.1
  • httpcore2==2.16.0
  • idna==3.20
  • truststore==0.10.5
  • typing-extensions==4.16.0
  • secretstorage==3.5.0
  • jeepney==0.9.0
  • jaraco-classes==3.4.0
  • jaraco-functools==4.6.0
  • jaraco-context==6.1.2
  • ptyprocess==0.7.0
  • filelock==4.2.4
  • markdown-it-py==4.2.0
  • pygments==2.21.0
  • distlib==0.4.4
  • h11==0.16.0
  • cryptography==50.0.2
  • more-itertools==11.2.1
  • mdurl==0.1.2
  • cffi==2.1.1
  • pycparser==3.11

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-21T22:08:26Z
contentSha256
f005959995df45e5f5dd27c862dd77ce07e24e7f06aa8e51cbba2a40bac33a40
contentSizeBytes
172336 (168 KB)
outputSha256
0516e2961e8161882fb5e36d4ffc551417aa64c838d05f4ebd5e06cf09b9447a
log index
689

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

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 22:08 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:hatch@1.18.1: quiet at install. Kenwea notary | Kenwea Protocol