EN 18031 / PSTI Device Config Lint

Lint IoT and radio device config, firmware defaults and device manifests against RED Art. 3(3)(d)(e)(f) (EN 18031-1/-2/-3) and the UK PSTI security requirements. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Get the complete version $29

This page is the working piece. The full pack has everything below.

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

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

Buy the full version — $29

Questions people ask

What does EN 18031 / PSTI Device Config Lint actually do?

It reads device config and firmware default files - device.yaml, prj.conf, mosquitto.conf, .env, C headers - and reports each line that fails RED Article 3(3)(d), (e) or (f) or a UK PSTI Schedule 1 duty. 19 rules, each finding carrying a line number, the article and the EN 18031 part the fix belongs to.

Who is this for?

Firmware and embedded engineers, and the compliance lead sitting next to them, at a company placing radio or connected equipment on the EU or UK market. If you are assembling a declaration of conformity for Delegated Regulation (EU) 2022/30, or answering a retailer's PSTI statement-of-compliance request, these are your files. Penalties under the PSTI Act 2022 reach 10 million pounds or 4% of qualifying worldwide revenue.

Why is a chatbot or a generic security linter not enough?

Generic linters look for secrets and syntax, not for legal duties, so they never ask whether a support period was published. Chatbots routinely cite EN 303 645 as the harmonised standard and repeat the withdrawn August 2024 date. This tool checks both mistakes explicitly, offline, against the file in front of you.

What is free and what needs the paid key?

Free and complete for one file: open it, run the check, see every finding with its line and clause, all 19 rules, no key and no account. The paid key adds a different job - sweeping every matching config in the workspace and exporting a dated evidence pack, Markdown plus CSV, that you keep and hand on.

What would this cost if a person did it?

A contract firmware engineer at $120 an hour bills roughly $480 for the half day it takes to walk one shipped-defaults file against Article 3(3)(d)(e)(f) and PSTI Schedule 1 by hand, and that half day repeats on every build. The full version is $29 once, with a 7-day full refund.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Want the full version?
Enter your email and we send the download link.
ENDEJAESPT

Find a tool