Metadata
Release files for mcp-travel-smart-plan 7.0.2
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.2.tar.gz | 14.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_travel_smart_plan-7.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.3 kB
Release files / mcp_travel_smart_plan-7.0.2.tar.gz
| Download URL | mcp_travel_smart_plan-7.0.2.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c813bccdcb1679b2c48dccd5c4b4688bfa40257893b26cfdf2b44776839bc4ca
|
|
BLAKE2b-256 checksum How to use checksums |
31ca6b286aab2d132f4a143baa47ee64581bdc2fea75de3ca522673ae685707d
|
| 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.2-py3-none-any.whl
| Download URL | mcp_travel_smart_plan-7.0.2-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63150d1b5209f3f65af50181f5c88e706963e8549b98e20ac11e0ead877219f8
|
|
BLAKE2b-256 checksum How to use checksums |
9995d20b56ecb330a6d8d0816810a9b589f4786a0c658fc2b897b5b4ecdc7c08
|
| 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.2
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.