A previous release had provenance metadata, but this release does not. View details.
mcpindex-preflight (EOL — frozen at 0.7.0)
End of life. This PyPI name is a deprecated alias frozen at 0.7.0. New installs must use
mcpindex-gate. Existinguv tool install mcpindex-preflight/uvx --from mcpindex-preflight …pins that already resolve to 0.7.0 keep working; no new alias versions will be published.
uv tool install mcpindex-gate
Python imports:
from mcpindex_gate import wrap, PreflightPin, PreflightHold
from mcpindex_preflight import … still re-exports the 0.7.0 API with a
DeprecationWarning, but that import path is unsupported for new work.
1 maintainer
Metadata
1 maintainer
Release files for mcpindex-preflight 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcpindex_preflight-0.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / mcpindex_preflight-0.7.1-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | mcpindex_preflight-0.7.1-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6a4c9534d80d5699a1db44bb44efc7005bd87f574b789184c598b25743334f2
|
|
BLAKE2b-256 checksum How to use checksums |
ee8d6903a3d06ec4965484724b18006efb090613fa131e0622a99088ff0c8e6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for mcpindex-preflight 0.7.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.7.0 1 file With provenance
- Added 0.7.1 1 file Without provenance
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
