xbsl
Инструментарий XBSL (1С:Элемент): линтер, LSP, документация, индекс проекта, скаффолдинг метаданных
Decision gist · record as of 2026-08-14
Yes, if you work with 1C:Element projects. XBSL is actively maintained, has no security vulnerabilities, low install friction, and a permissive MIT license. The toolkit is genuinely useful for catching issues before deploy and automating metadata scaffolding. The main prerequisite is extracting language data from your 1C:Element distribution; after that, it integrates smoothly into editors, CI, and AI workflows. Start with the linter and baseline if you have legacy code.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later.
- Language data must be extracted from your 1C:Element distribution before linting; the `xbsl extract --dist` command auto-detects your platform version and populates the data directory.
- Low install friction with a single runtime dependency (PyYAML).
License · maintenance · safety
MIT (permissive) — MIT license permits commercial and private use with minimal restrictions; you may use, modify, and distribute the package freely provided you include the license notice.
last release 2026-08-14 (0 days) · last repo commit 2026-08-14 · 1 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 92,782 downloads/mo, #13,425 on PyPI
Alternatives
Verify before relying
pip install xbsl
xbsl extract --dist ""
xbsl path/to/sources- Whether the package works with all current 1C:Element versions or only specific releases.
- Performance characteristics when linting large projects or running in CI pipelines.
- Whether the MCP server integration with Claude is production-ready or still experimental.
What it is and what it does
XBSL is a development toolkit for 1C:Element projects that operates on `.yaml` (element description) and `.xbsl` (code module) file pairs before server-side compilation. It provides a linter with 153 rules organized in four tiers—structure and schema validation, text and typography conventions, code structure analysis, and semantic verification against platform data—plus autofixes for mechanical issues like trailing whitespace and mixed newlines.
Beyond linting, XBSL offers metadata scaffolding to generate objects, attributes, routes, and forms without hand-writing YAML; an LSP server for editor integration (with a VS Code extension available); an MCP server for AI agent integration; documentation search over your distribution's reference; code templates; and CI integration with support for multiple output formats. The same core engine powers all four surfaces—CLI, LSP, MCP, and web UI—so every tool sees the same rules and data. A baseline mechanism lets you adopt rules on legacy codebases by freezing current findings and holding only new code to the rule.
Use it for
- Run local linting on 1C:Element projects before deploy to catch issues the server-side compiler misses.
- Generate and scaffold metadata objects, attributes, and forms from the command line without manual YAML editing.
- Integrate linting into CI/CD pipelines with exit codes and multiple output formats (text, JSON, CodeClimate).
- Use the VS Code extension for live diagnostics, go-to-definition, completion, and a form designer in your editor.
- Connect an AI agent to the MCP server to lint and create metadata objects in a single round trip.
- Adopt linting rules incrementally on legacy codebases using baseline snapshots to freeze existing findings.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you work with 1C:Element projects.
XBSL is actively maintained, has no security vulnerabilities, low install friction, and a permissive MIT license. The toolkit is genuinely useful for catching issues before deploy and automating metadata scaffolding. The main prerequisite is extracting language data from your 1C:Element distribution; after that, it integrates smoothly into editors, CI, and AI workflows. Start with the linter and baseline if you have legacy code.
Install
xbsl on PyPI
Before you install
Low install friction with a single runtime dependency (PyYAML). Active maintenance with a release on 2026-08-14 and recent repository activity. Requires Python 3.10 or later and an initial setup step to extract language data from your 1C:Element distribution before linting can begin.
Requires Python 3.10 or later. Language data must be extracted from your 1C:Element distribution before linting; the `xbsl extract --dist` command auto-detects your platform version and populates the data directory.
License in practice
MIT license permits commercial and private use with minimal restrictions; you may use, modify, and distribute the package freely provided you include the license notice.
Quickstart
pip install xbsl
xbsl extract --dist ""
xbsl path/to/sourcesVerify before relying
- Whether the package works with all current 1C:Element versions or only specific releases.
- Performance characteristics when linting large projects or running in CI pipelines.
- Whether the MCP server integration with Claude is production-ready or still experimental.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagePyYAML |
| Maintenance | Actively maintained 0 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 92,782 / month, #13,425 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaNatural Language :: RussianOperating System :: OS IndependentProgramming Language :: Python :: 3Topic :: Software Development :: Quality Assurance |
Evidence: xbsl-0.66.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “1c element linter”
- xbslXBSL is a linter, LSP server, and metadata scaffolding toolkit for…
- flake8-tupleA flake8 plugin that detects unintended one-element tuples in Python…
- flake8-annotations-complexityA flake8 plugin that flags type annotations exceeding configurable…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also taplo · rumdl · tclint · esbonio · skylos · njsscan · rstcheck-core · yamllint · python-lsp-ruff · skillsaw