← Back to home
Comparison · Infra & APIs

pakret vs slendr

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

pakret vs slendr: at a glance

Featurepakretslendr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesreproducible-documents, citations, bibtex, quartopopulation-genetics, simulation, tree-sequences, python-interop
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is pakret?

Package citation for R documents, quietly growing to meet Quarto.

pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.

Read the full pakret trajectory →

What is slendr?

Population-genetic simulation in R, opened up to selection and finally easier to install.

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

Read the full slendr trajectory →

pakret vs slendr: editorial side-by-side

P
pakret
INFRA · APIS
0.0

Package citation for R documents, quietly growing to meet Quarto.

◆ Current state

pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.

◆ Where it's heading

Every release in this window removes a specific friction someone hit while writing a document. Bib files that had to exist beforehand now get created; single-letter package names like R and C stopped being lower-cased in titles; the package works when loaded after conflicted; citing many packages got faster; and version numbers became optional for documents where they are noise. The 0.3.1 Quarto support extends the same idea to the format its users are moving to. Nothing here is architectural, and nothing needs to be.

◆ Prediction

Expect continued alignment with Quarto as more of its syntax surfaces become relevant, and further refinement of how multi-reference packages resolve to a single entry, which the BibTeX type priority work in 0.2.0 started. The entries give no indication of a 1.0.

S
slendr
INFRA · APIS
0.0

Population-genetic simulation in R, opened up to selection and finally easier to install.

◆ Current state

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

◆ Where it's heading

Since the 1.0.0 release added non-neutral simulation, the work has shifted from capability to friction. A large share of recent notes concerns Python environment handling, conda activation races on Windows, dependency pruning that made shiny optional, and argument names that misled users, as when gene_flow()'s rate argument turned out to mean total ancestry proportion rather than a rate. That is the profile of a package whose scientific surface is settled and whose remaining problems are the ones users actually hit.

◆ Prediction

Expect the uv-based environment path to move from fallback to default once it has proven itself, given the notes already describe an environment variable for making it so. The deprecated rate argument in gene_flow() is explicitly slated for removal in a future major release, which is the clearest signal here of what a 2.0 would contain.

Alternatives to pakret and slendr

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 pakret or slendr.

See all pakret alternatives → · See all slendr alternatives →

Recent activity from pakret and slendr

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

  1. 1mo agoslendrEphemeral uv Python environments remove the setup step
  2. 4mo agopakretQuarto inline syntax supported; list separators configurable
  3. 7mo agoslendrgene_flow() separates migration rate from ancestry proportion
  4. 8mo agopakretMissing .bib files created; capitalisation preserved
  5. 9mo agoslendrshiny made optional; SLiM 5.1 and Python 3.13 required
  6. 1y agoslendrconda activation reverted to a slower but reliable path
  7. 1y agoslendrBackends raised to SLiM 5.0, tskit 0.6.4 and msprime 1.3.4
  8. 1y agoslendrNon-neutral models arrive; slim() interface simplified
  9. 1y agopakretMultiple .bib files supported within one document
  10. 1y agopakretCitations with pre-written keys now supported
  11. 1y agopakretbook entries used when no manual entry exists

Frequently asked questions

What is the difference between pakret and slendr?

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

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

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

What are the best alternatives to slendr?

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