About ReadyStack
ReadyStack makes regulation-and-deadline linters: small, offline tools that read a real file (a SECURITY.md, a DORA register export, a signup form, a Dockerfile, an e-invoice) against a specific law or standard and name the line to fix, with the article next to it.
How the linters are made
- Each linter starts from the regulation text and the dates in it. Every rule carries its citation (an article, a WCAG success criterion, an ISO code) so you can check us.
- Before a linter is published it runs through an automated pipeline: the rules are executed against known-bad and known-good fixtures, the package is installed and run on a clean machine, and the marketplace listing is checked against what the tool actually does.
- The same engine ships four ways: VS Code and Open VSX extension, CLI on npm, Docker image, MCP server. One rule set, one version number.
What we do not do
- No watermarks, no counters, no crippled free tier. The per-file check is complete.
- No upload of your files. The check runs where the file is.
- No fake reviews. If you see a review, a person wrote it.
- No legal advice. A linter tells you what a rule says and where your file disagrees; a lawyer tells you what to do about it.
Who
An independent one-person studio in South Korea, run with an automated build-and-QA system. Contact: [email protected] · Support · security.txt.