ReadyStack for teams
For the person who has to prove the whole repository, not one file: compliance leads, platform teams, agencies shipping into the EU.
What the team key changes
- One key, every ReadyStack linter, 5 seats.
- Workspace sweep and dated report file for each linter (
--dir . --report html). --ci: exit 1 when an error-level finding exists, so the check gates the merge.- MCP
check_dirfor Claude Code, Cursor and any MCP client.
CI in three lines
- name: Regulation lint
run: npx -y @readystack/dora-register-lint --dir . --ci
env:
READYSTACK_LICENSE: ${{ secrets.READYSTACK_LICENSE }}Docker: docker run --rm -e READYSTACK_LICENSE -v "$PWD:/w" getreadystack/<name> /w --ci
What leaves the machine
The check itself runs offline; your files are never uploaded. There are exactly two network calls, both documented: licence validation against api.polar.sh when a key is entered, and an anonymous count (linter name only) when the key panel is shown, which respects the VS Code telemetry setting, DO_NOT_TRACK and READYSTACK_NO_TELEMETRY.
Procurement
Invoices with VAT come from Polar (merchant of record). For a quote, a purchase order or more than 5 seats, write to [email protected]. Security contact: security.txt.
Support
We answer within 2 business days at [email protected]. Include the linter name and version, your OS and the file type.