1 maintainer
Metadata
1 maintainer
Release files for mcp-transit-route 1.1.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_transit_route-1.1.2.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_transit_route-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / mcp_transit_route-1.1.2.tar.gz
| Download URL | mcp_transit_route-1.1.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b388380148cf880b6a764d087b00455b4a0841a87498b940e81d7bf1be1b269
|
|
BLAKE2b-256 checksum How to use checksums |
ead1264b97a6d8cf82d152b94ba0c9d8d3f6fe475ac2c1ac62d36cff017f4e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_transit_route-1.1.2-py3-none-any.whl
| Download URL | mcp_transit_route-1.1.2-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d73066cf18394c150b7fd87cf0134337e693d8e8cfabf80f082314ea7f25d8b3
|
|
BLAKE2b-256 checksum How to use checksums |
6aaf2612152e789cff4113eb55e8a9edfa533e9ab880fb599927ae348ccd6c5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-transit-route 1.1.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.
