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.
checktor()] as the top-level orchestrator,
running five categories of diagnostics (code, DESCRIPTION,
documentation, general, CRAN policy) against an R package
directory.checkup()] boolean wrapper for CI use,
[prescribe()] for treatment recommendations, and
[health_report()] for Markdown / HTML / text reports.xmlparsedata + xml2. Documentation-side
checks walk .Rd files via tools::parse_Rd().
DESCRIPTION is parsed with base::read.dcf().issues() (per-issue table), tidy() (per-check
table), summary() (per-category), plus
passed(), is_healthy(),
n_issues(), n_failed_checks(), and
failed_checks(). as.data.frame() on a result
is equivalent to tidy().NEWS file
(diagnose_news_file()) and README relative
links whose target is missing or excluded by .Rbuildignore
and so absent from the built tarball
(diagnose_readme_relative_links()).
diagnose_cran_comments_file() is also provided but, since a
cran-comments.md is a workflow convention rather than a
CRAN requirement, it is opt-in and not part of the default
checktor() run.Title fields of 65 or more
characters, single-quoted function names in
Title/Description (quotes are for software
names), and over-capitalized small words in the Title..Rd lacks
an \examples section
(diagnose_missing_examples()) and examples that use a
Suggested package without a requireNamespace() /
@examplesIf guard
(diagnose_suggested_in_examples()).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.