The author of this package has not provided a project description
Metadata
Release files for mcp-fliggy-travel 6.0.0
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_fliggy_travel-6.0.0.tar.gz | 14.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_fliggy_travel-6.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.7 kB
Release files / mcp_fliggy_travel-6.0.0.tar.gz
| Download URL | mcp_fliggy_travel-6.0.0.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce9192543184914829fcea40d4d65762961808a18fb7c491fd3c100034681c14
|
|
BLAKE2b-256 checksum How to use checksums |
ba0169475dc4c67cc97c1065aa575e979e307bb708927982877163711e607eb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_fliggy_travel-6.0.0-py3-none-any.whl
| Download URL | mcp_fliggy_travel-6.0.0-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8aeb0816161c9a57fc2d55ff5e90e3b029ad219131b48f8079eccd601209ae26
|
|
BLAKE2b-256 checksum How to use checksums |
83c0f73cd99363c2cf7c7bd690b23a3aa3555c9968ea07ce35b4afd300a4587d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-fliggy-travel 6.0.0
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.