Metadata
1 maintainer
Release files for meshagent-markitdown 0.55.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.55.0.tar.gz | 29.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_markitdown-0.55.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / meshagent_markitdown-0.55.0.tar.gz
| Download URL | meshagent_markitdown-0.55.0.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd0fa5de53af0c9ea32c1f2668215dcc62dec01c4f5597a8e9d747d102919a13
|
|
BLAKE2b-256 checksum How to use checksums |
e5fdfac0e487586a4e37f7c9667e8c512b3bb719380dba375a027385b1eff1bb
|
| 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.55.0-py3-none-any.whl
| Download URL | meshagent_markitdown-0.55.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34ad6347507aa50f45f68b1756f59facccfe0be117511d88b57102106aab9b23
|
|
BLAKE2b-256 checksum How to use checksums |
47b7230e617c78ddfe31c6ee7040a2595a5baed5dbfb194e15943e55d10e7714
|
| 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.55.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.
