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

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.71
File Size Uploaded
pain001_lsp-0.0.71.tar.gz 27.5 kB Details

Built distribution (wheel)

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

Total release size: 51.0 kB

Release files / pain001_lsp-0.0.71.tar.gz

Download URL pain001_lsp-0.0.71.tar.gz
Size 27.5 kB
Tags Source
SHA-256 checksum
How to use checksums
7565a639e7e9b545d32b1a24caa5f4832e5c944b21fd359ebc0128a2a2a6595f
BLAKE2b-256 checksum
How to use checksums
49fe86a1b185492d6b6ef44455e59e223db26e7dacd7b138ac9e001b11807c32
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 26, 2026.

Transparency log

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

Download URL pain001_lsp-0.0.71-py3-none-any.whl
Size 23.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bd30d5e9e38bb9b1c9098b1e35827a19357ab2d6bf6d930e63c17dce03ff5b7e
BLAKE2b-256 checksum
How to use checksums
b57864d8e6a48b9df062c8d96dfc53557188e28bd23a440a3d5d6af32d463e26
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 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.71 This release

2 release files

0.0.70

2 release files

0.0.69

2 release files

0.0.68

2 release files

0.0.67

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