← Back to home
Comparison · Infra & APIs

pkgcache vs Semgrep

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

pkgcache vs Semgrep: at a glance

FeaturepkgcacheSemgrep
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themespackage-management, r-lib, repositories, authenticationstatic-analysis, language-coverage, scan-performance, large-repo-scaling
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

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 →

What is Semgrep?

Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.

Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.

Read the full Semgrep trajectory →

pkgcache vs Semgrep: editorial side-by-side

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.

S
Semgrep
INFRA · APIS
5.0

Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.

◆ Current state

Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.

◆ Where it's heading

The performance work is converging on one problem: very large monorepos. File targeting now batches path filtering across worker domains, rule parsing shards by bytes instead of worker count, and a new Pro memory policy lets a scan trade RAM for skipping on-disk caching. Running alongside it is a quieter thread of trust work, and the 1.173.0 fix for silently dropped targets belongs to it: a file whose path filtering failed appeared in neither the findings nor the skipped list, which is the kind of gap that undermines a scan report more than any missing rule.

◆ Prediction

Expect the parser-refresh-plus-throughput cadence to continue, with the memory policy and the dependency-path output likely graduating out of experimental once large-repo users report back on them.

Alternatives to pkgcache and Semgrep

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

See all pkgcache alternatives → · See all Semgrep alternatives →

Recent activity from pkgcache and Semgrep

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

  1. 23h agoSemgrepSolidity parser refresh; batched targeting for very large repos
  2. 16d agoSemgrepOpenTofu files scanned as Terraform; Ruby parser updated
  3. 22d agoSemgrepBuild moves to a patched OCaml compiler to stop rare crashes
  4. 29d agoSemgrepPro C/C++ scans skip statically-dead preprocessor branches
  5. 1mo agoSemgrepDart parser updated to a newer upstream version
  6. 1mo agoSemgrepExperimental flag exposes full paths for transitive dependency findings
  7. 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
  8. 1y agopkgcacherepo_auth() brings authenticated repositories to the cache
  9. 1y agopkgcacheStops using source URLs for archived PPM packages
  10. 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
  11. 2y agopkgcacheImproves R to Bioconductor version matching
  12. 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added

Frequently asked questions

What is the difference between pkgcache and Semgrep?

They serve adjacent needs but don't currently overlap on shipped themes. Semgrep is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is pkgcache better than Semgrep?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Semgrep is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

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.

What are the best alternatives to Semgrep?

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