LaTeX Submission Lint: Desk-Reject Check
Runs the same checker as the npm package
@readystack/latex-submission-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Seventeen rules on your .tex file: the statements the editorial office looks for, and the source that breaks the publisher's build.
Install
latex-submission-lint file
Node 18+. The same 17 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the .tex file you have open against all 17 submission rules and writes a line-numbered report of every statement the publisher will look for and cannot find.
--ruleslists every rule
With a licence ($29 once)
- Runs the same 17 rules over every .tex file in the project, follows the include chain of a split manuscript, and exports one submission-readiness report for the whole paper.
@readystack/latex-submission-lint --dir ./templates --report html --out report.html
Manuscript editing services price per word, from about $0.05, so a 6,000-word paper runs to roughly $300 and a revision cycle takes days.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "latex-submission-lint": { "command": "npx", "args": ["-y", "@readystack/latex-submission-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: LaTeX Submission Lint: Desk-Reject Check
run: npx -y @readystack/latex-submission-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/latex-submission-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-latex-submission-lint
latex-submission-lint --help
Metadata
Release files for readystack-latex-submission-lint 1.0.8.post1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_latex_submission_lint-1.0.8.post1.tar.gz | 16.1 kB | Without provenance | Details for readystack_latex_submission_lint-1.0.8.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_latex_submission_lint-1.0.8.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_latex_submission_lint-1.0.8.post1-py3-none-any.whl |
Total release size: 34.4 kB
Release files / readystack_latex_submission_lint-1.0.8.post1.tar.gz
| Download URL | readystack_latex_submission_lint-1.0.8.post1.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d20fa4f028aef8f3506735f60dd33e43026dac00776e5588b6ece0b0cb426e54
|
|
BLAKE2b-256 checksum How to use checksums |
f688208b81f6ff4f750da0c00d7bb4ad6f7741566c63fa8b59a7a681b965576b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_latex_submission_lint-1.0.8.post1-py3-none-any.whl
| Download URL | readystack_latex_submission_lint-1.0.8.post1-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1762fc7978abb3f7ad058f96ff26e81f90044902a6e8dda35a01d3062ef5d40a
|
|
BLAKE2b-256 checksum How to use checksums |
d5b658033fc802ba6cca71dd6ba023b9b608b5376eb454a54b217e965c0b8289
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-latex-submission-lint 1.0.8.post1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.