The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mcp-train-ticket 2.0.4
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_train_ticket-2.0.4.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_train_ticket-2.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.6 kB
Release files / mcp_train_ticket-2.0.4.tar.gz
| Download URL | mcp_train_ticket-2.0.4.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e07c8139e5439a9672c2c3568695a628295c584c8509f1f95b8d5941c2c32a7
|
|
BLAKE2b-256 checksum How to use checksums |
6f4e478ce3ee129fa6cc0976cd1d4f9273d9dfdbdb976f778f64c24b45595183
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_train_ticket-2.0.4-py3-none-any.whl
| Download URL | mcp_train_ticket-2.0.4-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1095e222bdd26ca8ac52014ec34cd4cbacf05b9d04d020e359771c52efcbeb14
|
|
BLAKE2b-256 checksum How to use checksums |
4d4587e07b267741081cc17229d0441042fbbb7709c600c3735d822dd435acd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-train-ticket 2.0.4
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.
