The author of this package has not provided a project description
Metadata
Release files for mcp-fliggy-travel 6.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_fliggy_travel-6.0.1.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_fliggy_travel-6.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.0 kB
Release files / mcp_fliggy_travel-6.0.1.tar.gz
| Download URL | mcp_fliggy_travel-6.0.1.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8bfc5ec6330bdd23922fb5dc1765975be1bf21a3fdaca6f28a5d6d1a836cff51
|
|
BLAKE2b-256 checksum How to use checksums |
1cbc28983f78a72d6947bbf9f05eece83ffe544c93b0252768742b36c0bf1760
|
| 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.1-py3-none-any.whl
| Download URL | mcp_fliggy_travel-6.0.1-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f53c2580650ea7ea4f0e70aebb8166b9e72a423c62af78ce8f0d22d654ae999a
|
|
BLAKE2b-256 checksum How to use checksums |
e443905124106997e3028f949e58c2e8793cbcf32757e35a338051207cfa2aa7
|
| 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.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.