Notary record

pypi:librosa@1.0.0

PyPI · checked 21 Oct 2026, 23:13 UTC · checker 2026-10-19.2 · log index 930

Record issued 21 Oct 2026

Issued 21 Oct 2026, 23:13 UTC · pypi:librosa@1.0.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:librosa 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

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

Not installed:

  • numba>=0.61.0 (no wheel for this sandbox)
  • scikit-learn>=1.6.0 (no wheel for this sandbox)
  • soxr>=1.0.0 (no wheel for this sandbox)
Show all 19
  • numpy==2.5.4
  • scipy==1.18.1
  • joblib==1.6.0
  • decorator==5.3.1
  • soundfile==0.14.0
  • pooch==1.9.0
  • lazy-loader==0.6
  • msgpack==1.2.3
  • cloudpickle==3.1.2
  • cffi==2.1.1
  • typing-extensions==4.16.0
  • platformdirs==4.13.5
  • packaging==26.3
  • requests==2.34.2
  • pycparser==3.11
  • charset-normalizer==3.5.2
  • idna==3.20
  • urllib3==2.8.0
  • certifi==2026.10.19

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-21T23:13:41Z
contentSha256
5910a6c0e1b2e494b92758c1615a7acbd0515a2315e138927ba2982f2af88857
contentSizeBytes
294628 (288 KB)
outputSha256
31c939484ea5ca193692949d7e2d9b941a9ddf7d218bd0e0787ca0e90e33ba87
log index
930

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

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 23:13 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.