pypi:edgartools@5.60.0
PyPI · checked 21 Oct 2026, 21:00 UTC · checker 2026-10-19.2 · log index 441
Record issued 21 Oct 2026
Issued 21 Oct 2026, 21:00 UTC · pypi:edgartools@5.60.0
unfinished
The check could not finish. This is not a pass.
The check could not finish (entry_point_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.
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:edgartools 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
41 of 41 installed, as npm would on linux x64 musl.
Show all 41
- beautifulsoup4==4.15.0
- httpx==0.28.1
- httpxthrottlecache==0.7.0
- humanize==4.16.0
- jinja2==3.1.6
- lxml==6.1.3
- nest-asyncio==1.6.0
- orjson==3.13.0
- pandas==3.0.6
- pyarrow==26.0.0
- pydantic==2.14.1
- pyrate-limiter==4.5.1
- rank-bm25==0.2.2
- rapidfuzz==3.14.6
- rich==15.0.0
- stamina==26.1.0
- tabulate==0.10.0
- textdistance==4.6.3
- tqdm==4.70.1
- truststore==0.10.5
- unidecode==1.4.0
- soupsieve==3.0.3
- typing-extensions==4.16.0
- anyio==4.15.1
- certifi==2026.10.19
- httpcore==1.0.9
- idna==3.20
- aiofiles==25.1.0
- filelock==4.2.4
- markupsafe==3.0.4
- numpy==2.5.4
- python-dateutil==2.9.0.post0
- annotated-types==0.8.0
- pydantic-core==2.50.1
- typing-inspection==0.4.4
- markdown-it-py==4.2.0
- pygments==2.21.0
- tenacity==9.2.1
- h11==0.16.0
- six==1.17.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
- unfinished
- verdict
- manual_review
- reasonCode
- entry_point_failed
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T21:00:45Z
- contentSha256
- 4db917f3833f6b105fe78d22639172410c800ad6da260432884d86b53b88439b
- contentSizeBytes
- 3536327 (3.4 MB)
- outputSha256
- 8c4a7c0fce3068fc85c1f7c41e72a184261c84f7baa98c603cded572415ffdc6
- log index
- 441
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 21:00 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.