I kept losing days to things that were true last year: a Kubernetes manifest that still says extensions/v1beta1, a TLS cert plan written for 398 days when the cap is now 47, a Python project that ships without PEP 639 licence metadata, an SBOM that misses the fields the EU Cyber Resilience Act (reporting since 2026-09-11) expects.
So I built small, single-purpose linters that check the file open in your editor against the rule as it stands today, with the source of the rule (the statute or spec) on every finding. Each one is a separate VS Code extension (also on Open VSX for Cursor, as an npm CLI, and as a Docker image), with the same rules.json driving all forms.
The file open in the editor is free: no key, no counter, no limit. Sweeping a whole workspace and writing a dated report asks for a licence ($29 once, 7-day trial, 7-day refund). Source is public: readystack-themes (the extensions) and readystack-mcp (the same checks as MCP servers for AI agents).
Catalogue with a free web version of every check: getreadystack.com
Things I would genuinely like feedback on: which rules are wrong or stale (each finding cites its basis, so it should be easy to point at), and which deadlines you have to track that nothing checks yet.
Top comments (0)