B -->|compute_diagnostics / completion_items / hover_text / formatting / document_symbol| C["pain001"]
C -->|schema + IBAN/BIC validation| B
B -->|diagnostics · completion · hover · code action · format · outline| A
---
## When not to use pain001-lsp
- **You're not editing JSON payment data.** The server targets the
JSON record format consumed by the `pain001` generator; if you're
authoring the underlying XML directly, use a generic XSD-aware
language server.
- **You need CSV diagnostics in the editor.** The CSV diagnostic engine
ships in-tree under [`pain001[lsp]`](https://github.com/sebastienrousseau/pain001)
(`pain001-lsp-builtin`); this standalone server focuses on the
richer JSON surface.
- **You want agent tools, not editor diagnostics.** Use
[`pain001-mcp`](https://pypi.org/project/pain001-mcp/) — it speaks
the Model Context Protocol to AI assistants.
---
## Development
`pain001-lsp` uses [Poetry](https://python-poetry.org/) and
[mise](https://mise.jdx.dev/).
```bash
git clone https://github.com/sebastienrousseau/pain001-lsp.git
cd pain001-lsp
mise install
poetry install
A Makefile orchestrates the quality gates (kept in lockstep with CI):
| Target | What it runs |
|---|---|
make check |
All gates (REQUIRED before commit) |
make test |
pytest --cov=pain001_lsp --cov-branch --cov-fail-under=100 |
make lint |
ruff check + ruff format --check |
make type-check |
mypy --strict |
make examples |
Run the three example scripts |
Current state (v0.0.54): 81 tests passing, 100% line + branch
coverage against a 100% enforced floor, mypy --strict clean,
interrogate 100% docstring coverage.
Security
- No filesystem writes. The server reads from the editor's in-memory document buffer; no scratch files, no temp directories.
- JSON parsing uses the stdlib
jsonmodule on already-quoted text from the editor — noeval, no shelling out, no XML. - Validation failures are returned as
lsprotocol.Diagnosticobjects with no stack traces, so the editor never sees an internal path or exception message. - Dependencies are pinned via
poetry.lockand audited bypip-auditand Bandit in CI.
To report a vulnerability, please use GitHub private vulnerability reporting rather than a public issue.
Documentation
- Runnable examples:
examples/ - VS Code scaffold:
editors/vscode/ - Release history: CHANGELOG.md
- Core library docs: docs.pain001.com
- LSP specification: microsoft.github.io/language-server-protocol
Contributing
Contributions are welcome — see the
contributing instructions.
Thanks to all the
contributors
who have helped build pain001-lsp.
License
Licensed under the Apache License, Version 2.0.
Built on pygls and
lsprotocol by the
Open Law Library, and on the core
pain001 library that
powers the validators and schemas.
Any contribution submitted for inclusion shall be licensed as above, without additional terms.
pain001.com · PyPI · GitHub
Release files for pain001-lsp 0.0.63
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pain001_lsp-0.0.63.tar.gz | 24.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pain001_lsp-0.0.63-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.3 kB
Release files / pain001_lsp-0.0.63.tar.gz
| Download URL | pain001_lsp-0.0.63.tar.gz |
|---|---|
| Size | 24.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
028eb931cd9deff324b3f647e3730d9bc87147f5e122a5e46e974d85f26e80af
|
|
BLAKE2b-256 checksum How to use checksums |
1d6f82b00b632b7740a3c14ff591c88b5ea2b7e727dc5d9a8e9997280f16d23f
|
| 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 Aug 28, 2026.
Transparency logRelease files / pain001_lsp-0.0.63-py3-none-any.whl
| Download URL | pain001_lsp-0.0.63-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45e0242567b01882218178eb9fce7618d6b18dfbe6562497957afb314fded621
|
|
BLAKE2b-256 checksum How to use checksums |
fa558cf5cdff23f57953d383c76c92a51e99def47e9ad9207a1193e7c855d1bb
|
| 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 Aug 28, 2026.
Transparency log