Catch the CRAN Repository Policy violations before the volunteer team does
162
Catch the CRAN Repository Policy violations before the volunteer team does
docker run --rm -v "$PWD":/work getreadystack/cran-policy-submission-lint /work/file
The same 25 rules as the VS Code extension, in a container. Mount a folder on /work.
--rules lists every ruledocker run --rm -e READYSTACK_LICENSE=<key> -v "$PWD":/work getreadystack/cran-policy-submission-lint --dir /work --ci
A freelance R developer in North America bills $50-$100 an hour (Upwork, 2026); one rejected submission is a round trip of rework plus a wait in the queue.
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cran-policy-submission-lint": { "command": "npx", "args": ["-y", "@readystack/cran-policy-submission-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence; the full sweep is free for 7 days). The agent gets every finding with the line number.
- name: CRAN Policy Submission Lint
run: npx -y @readystack/cran-policy-submission-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/cran-policy-submission-lint --dir /work --ci)
Try the full run free for 7 days — no key needed. Then one licence, 7-day refund, no questions. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Content type
Image
Digest
sha256:d8e6b8ec6…
Size
46.1 MB
Last updated
4 days ago
docker pull getreadystack/cran-policy-submission-lint