← Back to home
Comparison · Infra & APIs

goodpractice vs pkgcache

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

goodpractice vs pkgcache: at a glance

Featuregoodpracticepkgcache
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescode-quality, static-analysis, r-package, ropenscipackage-management, r-lib, repositories, authentication
Last editorial update49m ago1h 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 pkgcache?

The metadata cache under pak now speaks to authenticated and corporate repositories.

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

Read the full pkgcache trajectory →

goodpractice vs pkgcache: 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.

P
pkgcache
INFRA · APIS
0.0

The metadata cache under pak now speaks to authenticated and corporate repositories.

◆ Current state

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

◆ Where it's heading

The work has shifted from CRAN-shaped assumptions toward the mixed reality of how R packages are actually distributed now — PPM snapshots, R Universe, private and authenticated registries, Bioconductor, and per-platform binaries across several R versions. Resilience is a recurring theme too: 2.2.5 makes an unreachable Bioconductor a non-fatal condition rather than a failure. MRAN's retirement, handled in 2.2.0 by resolving its prefix to PPM, is a reminder of how much of this package's job is absorbing other people's infrastructure changes.

◆ Prediction

Expect continued tracking of R-devel metadata format changes and new binary platforms as R 4.6 lands, since both already appear in 2.2.5. Further work on authenticated repository handling is the plausible follow-on, given how recently that capability arrived.

Alternatives to goodpractice and pkgcache

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 pkgcache.

See all goodpractice alternatives → · See all pkgcache alternatives →

Recent activity from goodpractice and pkgcache

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

  1. 2mo agogoodpracticeChecks organized into 16 selectable groups with presets
  2. 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
  3. 1y agopkgcacherepo_auth() brings authenticated repositories to the cache
  4. 1y agopkgcacheStops using source URLs for archived PPM packages
  5. 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
  6. 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
  7. 2y agopkgcacheImproves R to Bioconductor version matching
  8. 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added
  9. 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
  10. 5y agogoodpracticePackage logo added

Frequently asked questions

What is the difference between goodpractice and pkgcache?

They serve adjacent needs but don't currently overlap on shipped themes. goodpractice and pkgcache 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 pkgcache?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. goodpractice and pkgcache 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 pkgcache?

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