@readystack/en18031-psti-lint

EN 18031 / PSTI Device Config Lint

Line-by-line check of shipped device defaults against RED Art. 3(3)(d)(e)(f), EN 18031-1/-2/-3 and UK PSTI Schedule 1

Install

npx @readystack/en18031-psti-lint file

Node 18+. The same 19 rules as the VS Code extension, from a terminal or CI.

Free

• Lint the device config file open in the editor and get every RED Art. 3(3) / EN 18031 / PSTI finding with its line number and clause, all 19 rules, no key
• --rules lists every rule

With a licence ($29 once)

• Sweep every matching config in the workspace and export a dated evidence pack (Markdown + CSV) mapping each finding to its article and clause, kept as a document for the test lab

@readystack/en18031-psti-lint --dir ./templates --report html --out report.html

A contract firmware engineer at $120 an hour bills about $480 for the half day one shipped-defaults file takes by hand, and it repeats every build

Use from an AI agent (MCP)

Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:

{ "mcpServers": { "en18031-psti-lint": { "command": "npx", "args": ["-y", "@readystack/en18031-psti-lint", "--mcp"] } } }

Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.

Use in CI

- name: EN 18031 / PSTI Device Config Lint
  run: npx -y @readystack/en18031-psti-lint --dir . --ci

(container: docker run --rm -v "$PWD:/work" getreadystack/en18031-psti-lint --dir /work --ci)

The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.

Get a licence