← Back to home
Comparison · Infra & APIs

goodpractice vs quarto-r

A side-by-side editorial comparison of goodpractice and quarto-r — release velocity, themes, recent moves, and the top alternatives to consider.

goodpractice vs quarto-r: at a glance

Featuregoodpracticequarto-r
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescode-quality, static-analysis, r-package, ropensciquarto, publishing, cli-wrapper, r-packages
Last editorial update2h ago43m ago
WebsiteVisit →Visit →

What is goodpractice?

The R package-quality checker returns from CRAN limbo with checks you can select by category.

goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.

Read the full goodpractice trajectory →

What is quarto-r?

The R side of Quarto stopped being a render wrapper and became a project interface

The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.

Read the full quarto-r trajectory →

goodpractice vs quarto-r: editorial side-by-side

G
goodpractice
INFRA · APIS
0.0

The R package-quality checker returns from CRAN limbo with checks you can select by category.

◆ Current state

goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.

◆ Where it's heading

The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.

◆ Prediction

With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.

Q
quarto-r
INFRA · APIS
0.0

The R side of Quarto stopped being a render wrapper and became a project interface

◆ Current state

The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.

◆ Where it's heading

The package's job is to stay a faithful surface over a CLI it does not control, and the releases show what that costs. Version numbers track the Quarto release they target, tests are adapted around upstream regressions, and behaviour is reworked when the CLI changes — quarto_use_template() now errors clearly in non-empty directories because interactive prompting was never suitable for programmatic use. The 1.5.1 release exists entirely so CRAN checks pass on machines where Quarto is not installed at all.

◆ Prediction

Expect the next release to track the next Quarto CLI version, with the open question in the feed being how --no-prompt behaviour settles upstream for template use. Feature work here follows the CLI rather than leading it.

Alternatives to goodpractice and quarto-r

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either goodpractice or quarto-r.

See all goodpractice alternatives → · See all quarto-r alternatives →

Recent activity from goodpractice and quarto-r

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agogoodpracticeChecks organized into 16 selectable groups with presets
  2. 11mo agoquarto-rTests skip correctly when Quarto is not installed
  3. 1y agoquarto-routput_file moves to Quarto metadata, unlocking multi-format renders
  4. 2y agoquarto-rPreview URL detection fixed inside the RStudio viewer
  5. 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
  6. 2y agoquarto-rProject, extension and vignette support arrive alongside rendering
  7. 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
  8. 5y agogoodpracticePackage logo added

Frequently asked questions

What is the difference between goodpractice and quarto-r?

They serve adjacent needs but don't currently overlap on shipped themes. goodpractice and quarto-r are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is goodpractice better than quarto-r?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. goodpractice and quarto-r are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to goodpractice?

Top goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.

What are the best alternatives to quarto-r?

Top quarto-r alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "quarto-r alternatives" section above for the current picks, or visit /alternatives/quarto-r for the full list with editorial commentary on each.