import-linter-ls
A language server for import-linter, with a VS Code extension. See your architecture contract errors and import violations in the editor, not only in CI.
Status: early. The server starts and recognises import-linter config files. Diagnostics, hover and completion are coming. See the roadmap.
Use it in VS Code
-
Install the server in your project:
uv add --dev import-linter-ls # or: pip install import-linter-ls
-
Install the Import Linter extension. Until it is on the Marketplace, download the
.vsixfrom the latest release and run Extensions: Install from VSIX.... -
Select your project's Python environment (Python: Select Interpreter) and open your project.
It works with .importlinter, setup.cfg and pyproject.toml configs. Check Output > Import Linter for logs.
| Setting | Purpose |
|---|---|
importLinterLs.interpreter |
Python that has import-linter-ls. Empty: use the one selected in VS Code. |
importLinterLs.trace.server |
off, messages or verbose: log the editor/server messages. |
Command: Import Linter: Restart Language Server.
Use it in another editor
Any editor with an LSP client can run the server over stdio with import-linter-ls
(or python -m import_linter_ls).
Develop
uv sync && pnpm install
uv run prek install # git hooks
uv run pytest # unit + integration tests
To try the extension, open this folder in VS Code and press F5, then open examples/layered_app.
More in CONTRIBUTING.md and AGENTS.md.
Layout
| Path | What |
|---|---|
src/import_linter_ls/ |
The language server (Python, pygls). |
vscode-extension/ |
The VS Code extension (TypeScript), a thin client. |
examples/layered_app/ |
Example app with one broken contract, in TOML and INI. |
tests/ |
Unit and integration tests. |
docs/ |
Documentation site (zensical). |
1 maintainer
Metadata
1 maintainer
Release files for import-linter-ls 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 | Actions |
|---|---|---|---|---|
| import_linter_ls-0.1.0.tar.gz | 7.3 kB | With provenance | Details for import_linter_ls-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| import_linter_ls-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for import_linter_ls-0.1.0-py3-none-any.whl |
Total release size: 15.7 kB
Release files / import_linter_ls-0.1.0.tar.gz
| Download URL | import_linter_ls-0.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9aaa27d3cf77ed25a820bb18291d19909b937d59817f78e5b40d00d1726a82c
|
|
BLAKE2b-256 checksum How to use checksums |
9d0eae63355e573f1592ae5f09d86816500147c6384012d7d1152d19c92229ad
|
| 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 Nov 7, 2026.
Transparency logRelease files / import_linter_ls-0.1.0-py3-none-any.whl
| Download URL | import_linter_ls-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa1a5241f47bea060e02b75fdd8e4e1c9ede7389bec7a5bc781e88f4d665464a
|
|
BLAKE2b-256 checksum How to use checksums |
331c9a91040f6d1b01ec764949c4ea8ee36069c3f4ab5f590e1559992710696a
|
| 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 Nov 7, 2026.
Transparency logSecurity for import-linter-ls 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
Both files in this release have been uploaded with provenance metadata.
Attestation for import_linter_ls-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 Nov 7, 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.
