The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for starship-mcp 0.1.10
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 | |
|---|---|---|---|---|
| starship_mcp-0.1.10.tar.gz | 16.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| starship_mcp-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.2 kB
Release files / starship_mcp-0.1.10.tar.gz
| Download URL | starship_mcp-0.1.10.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc47632cb97ec06a0435a08c64dd9267d448847985d2708ce59b31d64765b60f
|
|
BLAKE2b-256 checksum How to use checksums |
c1dcba3981d22d2f11844b8e0d1bed7cc96e482fa91726f2a13f0970ae4046a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / starship_mcp-0.1.10-py3-none-any.whl
| Download URL | starship_mcp-0.1.10-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c44664fc24f473ac251aac2c1260c837be740abd9fec9d1fcfef2c3551099c1
|
|
BLAKE2b-256 checksum How to use checksums |
80e4f39de8de24fb44707f55a23eb4ddb09ea8a819aafd7dfe408298b4092f75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for starship-mcp 0.1.10
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.
