Meshagent
Meshagent Markitdown
Metadata
Release files for meshagent-markitdown 0.54.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| meshagent_markitdown-0.54.0.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_markitdown-0.54.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.7 kB
Release files / meshagent_markitdown-0.54.0.tar.gz
| Download URL | meshagent_markitdown-0.54.0.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a5f01158dd09daf41fff783761c1eb4d173d189abd60e0149d9686eb92a8445
|
|
BLAKE2b-256 checksum How to use checksums |
349b0f840a0085a9ce96144d1747b21cb2916d47068bfc2a4b102806b8d3783f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / meshagent_markitdown-0.54.0-py3-none-any.whl
| Download URL | meshagent_markitdown-0.54.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be765b86326a71d3c4af59da67938c53a5b2878ed8455187d727e7ea249a7e36
|
|
BLAKE2b-256 checksum How to use checksums |
0177ff43d3328efcd2f6791258a054184f033cb73d88857f706a853fc7d58819
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for meshagent-markitdown 0.54.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.