pypi:pip-audit@2.10.1
PyPI · checked 21 Oct 2026, 22:54 UTC · checker 2026-10-19.2 · log index 856
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:54 UTC · pypi:pip-audit@2.10.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.
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:pip-audit 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
28 of 28 installed, as npm would on linux x64 musl.
Show all 28
- cachecontrol==0.14.4
- cyclonedx-python-lib==11.12.0
- packaging==26.3
- pip-api==0.0.35
- pip-requirements-parser==32.0.1
- requests==2.34.2
- rich==15.0.0
- tomli==2.5.0
- tomli-w==1.2.0
- platformdirs==4.13.5
- msgpack==1.2.3
- filelock==4.2.4
- license-expression==30.4.4
- packageurl-python==0.17.6
- py-serializable==2.1.0
- sortedcontainers==2.4.0
- typing-extensions==4.16.0
- pip==26.2.2
- pyparsing==3.3.3
- charset-normalizer==3.5.2
- idna==3.20
- urllib3==2.8.0
- certifi==2026.10.19
- markdown-it-py==4.2.0
- pygments==2.21.0
- boolean-py==5.0
- defusedxml==0.7.1
- mdurl==0.1.2
Since the previous version
No comparison with an earlier version was made for this check.
Sandbox
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:54:53Z
- contentSha256
- 99ef3f600a317c1945f1e89e227ef26e1c2d618429b8bd3fa6f4f7c440c4611a
- contentSizeBytes
- 62023 (61 KB)
- outputSha256
- fd52eb2d1d309e04b1a7d9d8c0e6c5d26b6f8b34cb42402ea0b6a8eb06907f28
- log index
- 856
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:54 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.