The author of this package has not provided a project description
Metadata
Release files for flightsim-mcp 0.1.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 | |
|---|---|---|---|---|
| flightsim_mcp-0.1.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flightsim_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.7 kB
Release files / flightsim_mcp-0.1.0.tar.gz
| Download URL | flightsim_mcp-0.1.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
913669f87db2e98e17499ccdde4fa1df546d70fe762864161880abde1556f8cc
|
|
BLAKE2b-256 checksum How to use checksums |
9f39efc52d9e0165c768a60cb62d1237932a1f9ac61ea1200d90d1c0154648ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Release files / flightsim_mcp-0.1.0-py3-none-any.whl
| Download URL | flightsim_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcdb70150cbafe13cd6e5cb4bd93877d35d43c2be442c7408db3d0bb8ed81a16
|
|
BLAKE2b-256 checksum How to use checksums |
255518a007be5076dc6a7ff6dc6387ddf996a0a7a54f1bcdda0cab46620767a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Security for flightsim-mcp 0.1.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.