CVE-info
CVE-info is an alias distribution for
CVE-info-MCP.
It installs the same implementation and exposes the cve-info command.
uvx cve-info install --client claude-desktop
Python 3.11+ and uv are required for this command. See the main documentation for data updates, local MCP clients, and Web-client connection limitations. PyPI package names are case-insensitive; both distributions resolve equally with uppercase or lowercase spelling.
1 maintainer
Metadata
1 maintainer
Release files for CVE-info 0.1.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 | |
|---|---|---|---|---|
| cve_info-0.1.0.tar.gz | 2.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cve_info-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / cve_info-0.1.0.tar.gz
| Download URL | cve_info-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec7ff241c21d32c346c635554a41f69dd0ed6b63cfadd1146b7fd5df6170efab
|
|
BLAKE2b-256 checksum How to use checksums |
b2318ff3e326c1e4e7b0a795c7f42810847148d6c9cd413aa63d408d33fa7e67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / cve_info-0.1.0-py3-none-any.whl
| Download URL | cve_info-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5cb148f9b0e21fd0be7b2b8c83d15d6ea948d662faf0c494f0c6c96656ed26a
|
|
BLAKE2b-256 checksum How to use checksums |
a7eea9c98aff0932f47cbe37e6e9d97d59cee2730b69503fef3c75c860b313b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for CVE-info 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cve_info-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
