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.
Checks adherence to a given style, syntax errors and possible semantic issues. Supports on the fly checking of R code edited with 'RStudio IDE', 'Emacs', 'Vim', 'Sublime Text', 'Atom' and 'Visual Studio Code'.
Version: | 3.1.2 |
Depends: | R (≥ 3.5) |
Imports: | backports (≥ 1.1.7), codetools, cyclocomp, digest, glue, knitr, rex, stats, utils, xml2 (≥ 1.0.0), xmlparsedata (≥ 1.0.5) |
Suggests: | bookdown, crayon, httr (≥ 1.2.1), jsonlite, mockery, patrick, rlang, rmarkdown, rstudioapi (≥ 0.2), testthat (≥ 3.1.5), tibble, tufte, withr (≥ 2.5.0) |
Enhances: | data.table |
Published: | 2024-03-25 |
DOI: | 10.32614/CRAN.package.lintr |
Author: | Jim Hester [aut], Florent Angly [aut] (fangly), Russ Hyde [aut], Michael Chirico [aut, cre], Kun Ren [aut], Alexander Rosenstock [aut] (AshesITR), Indrajeet Patil [aut] (@patilindrajeets) |
Maintainer: | Michael Chirico <michaelchirico4 at gmail.com> |
BugReports: | https://github.com/r-lib/lintr/issues |
License: | MIT + file LICENSE |
URL: | https://github.com/r-lib/lintr, https://lintr.r-lib.org |
NeedsCompilation: | no |
Language: | en-US |
Materials: | README NEWS |
CRAN checks: | lintr results |
Reference manual: | lintr.pdf |
Vignettes: |
Continuous integration Creating new linters Editor setup Using lintr |
Package source: | lintr_3.1.2.tar.gz |
Windows binaries: | r-devel: lintr_3.1.2.zip, r-release: lintr_3.1.2.zip, r-oldrel: lintr_3.1.2.zip |
macOS binaries: | r-release (arm64): lintr_3.1.2.tgz, r-oldrel (arm64): lintr_3.1.2.tgz, r-release (x86_64): lintr_3.1.2.tgz, r-oldrel (x86_64): lintr_3.1.2.tgz |
Old sources: | lintr archive |
Please use the canonical form https://CRAN.R-project.org/package=lintr 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.