1 maintainer
Metadata
1 maintainer
Release files for mcp-rollinggo-hotel 1.5.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_rollinggo_hotel-1.5.2.tar.gz | 14.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_rollinggo_hotel-1.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.1 kB
Release files / mcp_rollinggo_hotel-1.5.2.tar.gz
| Download URL | mcp_rollinggo_hotel-1.5.2.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a402e4061756fd2ebf5909e5a58d7a67b3ea3b50d7aa619cf42464643d495a4d
|
|
BLAKE2b-256 checksum How to use checksums |
48f3bd43f740f23ac6a428d3d5003de7649c2597bd853e886abedceef8bd665a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_rollinggo_hotel-1.5.2-py3-none-any.whl
| Download URL | mcp_rollinggo_hotel-1.5.2-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba636807c6db633c2c14bd86a705d73ae306ac12dde48708830cd40a03a1a3bb
|
|
BLAKE2b-256 checksum How to use checksums |
1321f3291194b442ec7b4cd8e86ed601d59769eddf0772c7a075157d4f630178
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-rollinggo-hotel 1.5.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.
