The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for vicsia-email-mcp 0.3.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 | |
|---|---|---|---|---|
| vicsia_email_mcp-0.3.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vicsia_email_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 kB
Release files / vicsia_email_mcp-0.3.0.tar.gz
| Download URL | vicsia_email_mcp-0.3.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3ecc3e9954236c6a5f54bdad52d817b4eccc6da616a3ade8680575f4da3d261
|
|
BLAKE2b-256 checksum How to use checksums |
8ba1564e74680d11b153805af165c2e1cbb27442c4b47d8ea59b01ff37ffeae5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Release files / vicsia_email_mcp-0.3.0-py3-none-any.whl
| Download URL | vicsia_email_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2874077cf34e0d1edab2c669b387cde95787974cb3245897c40877d147c45009
|
|
BLAKE2b-256 checksum How to use checksums |
2a4fa9d828f38a26e3e87b239ec622d89414af4e254fb8e5ea8a7746077df07d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Security for vicsia-email-mcp 0.3.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.
