Notary record

pypi:ffsubsync@0.5.1

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 23:13 UTC · pypi:ffsubsync@0.5.1

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

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

Not installed:

  • auditok==0.1.5 (no wheel for this sandbox)
  • srt>=3.0.0 (no wheel for this sandbox)
Show all 14
  • chardet==7.7.0
  • charset-normalizer==3.5.2
  • faust-cchardet==3.2.0
  • ffmpeg-python==0.2.0
  • numpy==2.5.4
  • pysubs2==1.9.0
  • rich==15.0.0
  • tqdm==4.70.1
  • typing-extensions==4.16.0
  • webrtcvad-wheels==2.0.14.post1
  • future==1.0.0
  • markdown-it-py==4.2.0
  • pygments==2.21.0
  • mdurl==0.1.2

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:13:49Z
contentSha256
a312ea5d3c7e3e15a13565b2327022e2568ed6f12104b3ecf940ec4566d9ab4e
contentSizeBytes
65508 (64 KB)
outputSha256
3c07590fa1a0228f93553a1e6fa4b5d0eb4868ad062319e8277837bb53702287
log index
931

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.