1 maintainer
Metadata
1 maintainer
Release files for mcp-trainer 0.1.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 | |
|---|---|---|---|---|
| mcp_trainer-0.1.0.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_trainer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.5 kB
Release files / mcp_trainer-0.1.0.tar.gz
| Download URL | mcp_trainer-0.1.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba663eacd32ded0f0e4cc796aabb481c09d5ba5f337b4991983881ef45f00ca6
|
|
BLAKE2b-256 checksum How to use checksums |
0fb58bea65cccfe43af6d654226fc3e761b86e3fe5d230b115e6651948420667
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.12
|
Release files / mcp_trainer-0.1.0-py3-none-any.whl
| Download URL | mcp_trainer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc808d19d7efaa525952035786194ece9b60140fc78989ecc1066c40b4c18ccc
|
|
BLAKE2b-256 checksum How to use checksums |
8e44cadc017e3384e1a02261c90e06938a36306e1b2cd24db102eed371a1f815
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.12
|
Security for mcp-trainer 0.1.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.
