Skip to main content
|LSP over stdio| B["pain001-lsp"]
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 json module on already-quoted text from the editor — no eval, no shelling out, no XML.
  • Validation failures are returned as lsprotocol.Diagnostic objects with no stack traces, so the editor never sees an internal path or exception message.
  • Dependencies are pinned via poetry.lock and audited by pip-audit and Bandit in CI.

To report a vulnerability, please use GitHub private vulnerability reporting rather than a public issue.


Documentation


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.67

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pain001-lsp 0.0.67
File Size Uploaded
pain001_lsp-0.0.67.tar.gz 26.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pain001-lsp 0.0.67
File Interpreter ABI Platform
pain001_lsp-0.0.67-py3-none-any.whl Python 3 none any Details

Total release size: 50.0 kB

Release files / pain001_lsp-0.0.67.tar.gz

Download URL pain001_lsp-0.0.67.tar.gz
Size 26.8 kB
Tags Source
SHA-256 checksum
How to use checksums
74d3dac9ad672b2f40a68f958cdec933356da0ad81e956095a5afe798f621ae4
BLAKE2b-256 checksum
How to use checksums
f6601597ec00b1fb1a4baeae53347c2a707e4b36a8a8ee0979e17466502cefab
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 12, 2026.

Transparency log

Release files / pain001_lsp-0.0.67-py3-none-any.whl

Download URL pain001_lsp-0.0.67-py3-none-any.whl
Size 23.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
94208d4bcddf343c4f7dff18d219c70f4d9e227ba9961fc485b35e6da4eb4dd2
BLAKE2b-256 checksum
How to use checksums
c756bc4d07d5b8caea5ac1e36c685703c34a3e0568cb70f9c5879af3b4c6eb70
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 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.71

2 release files

0.0.70

2 release files

0.0.69

2 release files

0.0.68

2 release files

This release

0.0.67 This release

2 release files

0.0.66

2 release files

0.0.65

2 release files

0.0.64

2 release files

0.0.63

2 release files

0.0.62

2 release files

0.0.61

2 release files

0.0.60

2 release files

0.0.59

2 release files

0.0.54

2 release files

0.0.53

2 release files

0.0.52

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page