Metadata
Release files for mcp-travel-smart-plan 7.0.1
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_travel_smart_plan-7.0.1.tar.gz | 13.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_travel_smart_plan-7.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.6 kB
Release files / mcp_travel_smart_plan-7.0.1.tar.gz
| Download URL | mcp_travel_smart_plan-7.0.1.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ff9bde88b47696971b10d29a31541ced5e5a800b6f48f2a6b5378e46d4efe26
|
|
BLAKE2b-256 checksum How to use checksums |
2bb436e61acdacaee9cd2cbbba0a513a2d51f647644f33bd0cc39554272238e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / mcp_travel_smart_plan-7.0.1-py3-none-any.whl
| Download URL | mcp_travel_smart_plan-7.0.1-py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
760e17e7fd24627e9b568fcc1f0596f71718386b0434a89570afba1d1ae9eef7
|
|
BLAKE2b-256 checksum How to use checksums |
b877beb95fa0839a4adedcd4941aab25d4d005f09a0ebfc4914c9d53c46543bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for mcp-travel-smart-plan 7.0.1
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.