1 maintainer
Metadata
1 maintainer
Release files for mcp-self-drive-planner 1.2.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_self_drive_planner-1.2.2.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_self_drive_planner-1.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / mcp_self_drive_planner-1.2.2.tar.gz
| Download URL | mcp_self_drive_planner-1.2.2.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c84b8992f3db5dac92f41d7ce43873b4866f6313e1d89eae5656a54f7714301a
|
|
BLAKE2b-256 checksum How to use checksums |
7993d264e10e34b500aa4667d2d0c660fb53024ee5841d1f5490225f899b99ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / mcp_self_drive_planner-1.2.2-py3-none-any.whl
| Download URL | mcp_self_drive_planner-1.2.2-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
020b16b55d3733683b3194570c944507e51a5c6c4f59d983a1aa3d0ee56b2bfd
|
|
BLAKE2b-256 checksum How to use checksums |
795f15f6d90b38902a1281710459cb63b91e8e8b36e9ea6c39f7171e97b06f2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for mcp-self-drive-planner 1.2.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.
