pypi:funasr@1.4.16
PyPI · checked 21 Oct 2026, 22:10 UTC · checker 2026-10-19.2 · log index 693
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:10 UTC · pypi:funasr@1.4.16
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:funasr 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
- ldconfig, python3
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
- Looked for
- ld
First import
No first import was recorded for this check.
Dependencies
60 of 60 installed, as npm would on linux x64 musl. The tree is not complete.
Not installed:
- antlr4-python3-runtime==4.9.* (no wheel for this sandbox)
- jieba (no wheel for this sandbox)
- llvmlite>=0.38 (no wheel for this sandbox)
- numba>=0.51.2 (no wheel for this sandbox)
- numba>=0.55.0 (no wheel for this sandbox)
- numba>=0.61.0 (no wheel for this sandbox)
- omegaconf<2.4,>=2.2 (wanted by hydra-core; 2.4.0 is installed)
- oss2 (no wheel for this sandbox)
- scikit-learn>=0.18 (no wheel for this sandbox)
- scikit-learn>=1.6 (no wheel for this sandbox)
- scikit-learn>=1.6.0 (no wheel for this sandbox)
- sentencepiece (no wheel for this sandbox)
- soxr>=1.0.0 (no wheel for this sandbox)
Show all 60
- scipy==1.18.1
- librosa==1.0.0
- soundfile==0.14.0
- numpy==2.5.4
- pyyaml==6.0.3
- tqdm==4.70.1
- requests==2.34.2
- regex==2026.9.29
- websockets==17.3
- omegaconf==2.4.0
- hydra-core==1.3.7
- modelscope==1.40.2
- huggingface-hub==2.2.0
- safetensors==0.8.0
- transformers==5.20.2
- tiktoken==0.14.0
- kaldiio==2.18.1
- jamo==0.4.1
- jaconv==0.5.0
- umap-learn==0.5.12
- rapidfuzz==3.14.6
- torch-complex==0.4.4
- tensorboardx==2.6.5
- joblib==1.6.0
- decorator==5.3.1
- pooch==1.9.0
- lazy-loader==0.6
- msgpack==1.2.3
- cffi==2.1.1
- typing-extensions==4.16.0
- charset-normalizer==3.5.2
- idna==3.20
- urllib3==2.8.0
- certifi==2026.10.19
- packaging==26.3
- filelock==4.2.4
- modelscope-hub==0.4.6
- setuptools==84.2.1
- click==8.5.0
- fsspec==2026.9.0
- hf-xet==1.7.0
- httpx2==2.16.0
- tokenizers==0.23.3
- typer==0.27.3
- pynndescent==0.6.0
- protobuf==7.36.2
- cloudpickle==3.1.2
- platformdirs==4.13.5
- pycparser==3.11
- cryptography==50.0.2
- anyio==4.15.1
- httpcore2==2.16.0
- truststore==0.10.5
- shellingham==1.5.4
- rich==15.0.0
- annotated-doc==0.0.5
- h11==0.16.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
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:10:28Z
- contentSha256
- f95943f6a8111349a1b08907363b048a49e9cb9caa1e3afd8c92970d08bf450d
- contentSizeBytes
- 999588 (976 KB)
- outputSha256
- d45865edc8ccf0ebf082604570875dca320fc231866d30c4403740f826a67b16
- log index
- 693
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:10 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.