1 maintainer
Metadata
1 maintainer
Release files for friese-mcp 0.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 | |
|---|---|---|---|---|
| friese_mcp-0.0.1.tar.gz | 4.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| friese_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.2 kB
Release files / friese_mcp-0.0.1.tar.gz
| Download URL | friese_mcp-0.0.1.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f52a25779758ca1ba603bfcdc585abf16479a93350341370fa5bff543dfd7206
|
|
BLAKE2b-256 checksum How to use checksums |
0d6caeab501d1a421a74118033b17691e2c982e34990acb5ec0ee3e5ea21f25a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.10
|
Release files / friese_mcp-0.0.1-py3-none-any.whl
| Download URL | friese_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
662f2bd611d0fd2274da8ee622447db65cbecbe4bff55bd927c733645f1fe9c5
|
|
BLAKE2b-256 checksum How to use checksums |
eb3691574fd4ba2c12e199fcecebdef62a1de350a33ad08f90eff8aceabada48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.10
|
Security for friese-mcp 0.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.
