The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

jsslintr: JSS 'LaTeX'/'BibTeX' Style Checker

Lints 'LaTeX'/'BibTeX' manuscripts against the Journal of Statistical Software (JSS) style guide. Wraps the same 'Rust' rule engine used by the standalone 'jsslint' binary, the browser/'WASM' build, and the 'Python' binding, exposed to R via 'extendr'.

Version: 1.1.0-2
Depends: R (≥ 4.2)
Suggests: knitr, rmarkdown, testthat (≥ 3.0.0)
Published: 2026-07-29
DOI: 10.32614/CRAN.package.jsslintr
Author: Manuel Koller ORCID iD [aut, cre], The authors of the vendored 'Rust' crates [cph] (see inst/AUTHORS for details)
jsslintr author details
Maintainer: Manuel Koller <kollerma at proton.me>
BugReports: https://github.com/kollerma/jss-style-checker/issues
License: MIT + file LICENSE
Copyright: See the file inst/AUTHORS for the authors and copyright holders of the vendored 'Rust' dependency crates.
URL: https://github.com/kollerma/jss-style-checker, https://kollerma.github.io/jss-style-checker/
NeedsCompilation: yes
SystemRequirements: Cargo (Rust's package manager), rustc >= 1.85
CRAN checks: jsslintr results

Documentation:

Reference manual: jsslintr.html , jsslintr.pdf
Vignettes: Checking a Paper with jsslintr (source, R code)

Downloads:

Package source: jsslintr_1.1.0-2.tar.gz
Windows binaries: r-devel: jsslintr_1.1.0-2.zip, r-release: jsslintr_1.1.0-2.zip, r-oldrel: jsslintr_1.1.0-2.zip
macOS binaries: r-release (arm64): jsslintr_1.1.0-2.tgz, r-oldrel (arm64): jsslintr_1.1.0-2.tgz, r-release (x86_64): jsslintr_1.1.0-2.tgz, r-oldrel (x86_64): jsslintr_1.1.0-2.tgz
Old sources: jsslintr archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=jsslintr to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.