Notary record

pypi:rembg@2.0.85

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 23:12 UTC · pypi:rembg@2.0.85

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

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

Not installed:

  • numba>=0.60.0 (no wheel for this sandbox)
Show all 24
  • jsonschema==4.26.0
  • numpy==2.5.4
  • pillow==12.3.0
  • pooch==1.9.0
  • pymatting==1.1.16
  • scikit-image==0.26.0
  • scipy==1.18.1
  • tqdm==4.70.1
  • attrs==26.1.0
  • jsonschema-specifications==2025.9.1
  • referencing==0.37.0
  • rpds-py==2026.9.1
  • platformdirs==4.13.5
  • packaging==26.3
  • requests==2.34.2
  • networkx==3.7
  • imageio==2.38.1
  • tifffile==2026.10.15
  • lazy-loader==0.6
  • typing-extensions==4.16.0
  • 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
unfinished
verdict
manual_review
reasonCode
import_failed
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T23:12:45Z
contentSha256
9642672c3e879d576d0270ccfeada3d1c75585b9c78a7970d53a5c6874c0c1f2
contentSizeBytes
62845 (61 KB)
outputSha256
fbb12390e8b7679bd4c77974f2c1216673b94863281cbd46622717d97817ae7f
log index
927

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

Inclusion proofCheckpointKey list

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