Metadata
Release files for mcp-hotel-smart-book 2.0.3
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_hotel_smart_book-2.0.3.tar.gz | 8.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_hotel_smart_book-2.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / mcp_hotel_smart_book-2.0.3.tar.gz
| Download URL | mcp_hotel_smart_book-2.0.3.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a50ddd8098b80fb98097bb455f3e322c4215dc33ff056d03c5fd31d1bfcfbf8
|
|
BLAKE2b-256 checksum How to use checksums |
e527a8b1f81bb93ede9e47c6f682c3041b38ba547576d12cbc240a744e93a056
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_hotel_smart_book-2.0.3-py3-none-any.whl
| Download URL | mcp_hotel_smart_book-2.0.3-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
294d7ec60d5c6be3c8fc93cd8a0b22b4be52a60602d2759ca3c567c2326c506e
|
|
BLAKE2b-256 checksum How to use checksums |
4319bcfde2430a6a61082ee424ce42b8e099449045a69c3bb21121ba10ebf8bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-hotel-smart-book 2.0.3
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.