code-reality-lsp-bridge
The type-face MCP bridge: routes by file extension — .py tool calls
(hover / check_file / edit_file / lsp_status) go to a lazily spawned
pyrefly-lsp backend, .rs calls to rust-analyzer. One backend
session per language, independent lifecycles; the bridge itself does
no type analysis, it speaks LSP to the backends.
Backends are system-level installs (pyrefly-lsp ships in the
pyrefly-producer distribution; rustup component add rust-analyzer
for the Rust face) — missing backends surface as loud tool errors on
first use.
See the repository README for the tool semantics.
Metadata
Release files for code-reality-lsp-bridge 0.6.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| code_reality_lsp_bridge-0.6.8-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for code_reality_lsp_bridge-0.6.8-py3-none-macosx_11_0_arm64.whl |
Release files / code_reality_lsp_bridge-0.6.8-py3-none-macosx_11_0_arm64.whl
| Download URL | code_reality_lsp_bridge-0.6.8-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e7e017de2557e2afc0d191cef3e731593ab71f01017900951ee03eaaa8b430c1
|
|
BLAKE2b-256 checksum How to use checksums |
f789a13fcc554402f5b4d23f25d783eaa60a6b65bc03abefb66fcc9081dfa45d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 9, 2026.
Transparency logSecurity for code-reality-lsp-bridge 0.6.8
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 1 file in this release has been uploaded with provenance metadata.
Attestation for code_reality_lsp_bridge-0.6.8-py3-none-macosx_11_0_arm64.whl
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 Sep 9, 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.