← Back to home
Comparison · Analytics

pkglite vs textreuse

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

pkglite vs textreuse: at a glance

Featurepkglitetextreuse
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesr-packages, pharma-submissions, packaging, file-handlingtext-reuse, minhash, lsh, r-package
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is pkglite?

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

Read the full pkglite trajectory →

What is textreuse?

A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.

textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.

Read the full textreuse trajectory →

pkglite vs textreuse: editorial side-by-side

P
pkglite
ANALYTICS
0.0

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

◆ Current state

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

◆ Where it's heading

The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.

◆ Prediction

Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.

T
textreuse
ANALYTICS
2.5

A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.

◆ Current state

textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.

◆ Where it's heading

The arc here is restoration rather than expansion. The work has gone into making the package survivable — silencing deprecated dplyr and tidyr selection and many-to-many join warnings, moving from dead Travis and AppVeyor configs to GitHub Actions, and validating across five R platform and version combinations. Release notes now lead with verification evidence rather than features, which is the signature of a maintainer stabilizing an inherited codebase.

◆ Prediction

Expect continued compatibility releases tracking tidyverse deprecations; nothing in these entries indicates new hashing or alignment capability is planned.

Alternatives to pkglite and textreuse

Other Analytics 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 pkglite or textreuse.

See all pkglite alternatives → · See all textreuse alternatives →

Recent activity from pkglite and textreuse

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

  1. 20d agotextreuseCompatibility pass for current dplyr and tidyr
  2. 3mo agotextreuseCRAN resubmission fixing a moved README URL
  3. 3mo agotextreuse1.0.0 consolidates years of accumulated feature work
  4. 5mo agopkgliteMaintainer email and CI workflow updates
  5. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  6. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  7. 2y agopkgliteTest helpers moved to helper.R
  8. 3y agopkgliteMore file types recognised; cli dependency dropped
  9. 5y agopkgliteFile collections gain merge, prune, and a tests template
  10. 10y agotextreuseMinhashes split out from hashes in document objects

Frequently asked questions

What is the difference between pkglite and textreuse?

They serve adjacent needs but don't currently overlap on shipped themes. textreuse is currently shipping more aggressively (velocity 2.5 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 pkglite better than textreuse?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. textreuse is currently shipping more aggressively (velocity 2.5 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 Analytics products to evaluate alongside.

What are the best alternatives to pkglite?

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

What are the best alternatives to textreuse?

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