← Back to home
Comparison · Infra & APIs

carrier vs contagionchannels

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

Shared themes:r-package

carrier vs contagionchannels: at a glance

Featurecarriercontagionchannels
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, serialization, remote-execution, r-libeconometrics, contagion-analysis, cran-submission, r-package
Last editorial update5d ago1h ago
WebsiteVisit →Visit →

What is carrier?

carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.

carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.

Read the full carrier trajectory →

What is contagionchannels?

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

Read the full contagionchannels trajectory →

carrier vs contagionchannels: editorial side-by-side

C
carrier
INFRA · APIS
0.0

carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.

◆ Current state

carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.

◆ Where it's heading

Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.

◆ Prediction

The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.

C
contagionchannels
INFRA · APIS
0.0

Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.

◆ Current state

contagionchannels reached CRAN on 2026-05-08 with a methodology preprint behind it and a cross-quantilogram lineage visible in its citations. What the release feed does not contain is any description of what the package computes: all three entries document the submission process — a licence field reduced from GPL-3 plus file to plain GPL-3, an arXiv reference rewritten in canonical DOI form, and a base-graphics fallback adjusted on a reviewer's request.

◆ Where it's heading

There is no product trajectory to read here yet, only a submission one, and it is unusually well documented — each entry names the reviewer or check that prompted it and quotes the feedback verbatim. That transparency is the one signal available: the maintainer treats review rounds as releases worth publishing rather than squashing. Any judgement about direction will have to wait for a release that changes the package rather than its metadata.

◆ Prediction

With CRAN acceptance secured, the next release should be the first to carry actual methodological content; until one appears, there is not enough in these entries to say where the package is heading.

Alternatives to carrier and contagionchannels

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 carrier or contagionchannels.

See all carrier alternatives → · See all contagionchannels alternatives →

Recent activity from carrier and contagionchannels

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

  1. 3mo agocontagionchannelsv0.1.3 — first CRAN release
  2. 3mo agocontagionchannelsv0.1.2: switch arXiv reference in DESCRIPTION to canonical DOI form
  3. 3mo agocontagionchannelsv0.1.1: address CRAN reviewer feedback (License) + add arXiv reference
  4. 11mo agocarrierCrated helper functions can now see each other
  5. 1y agocarriercrate() gains .parent_env and stricter argument handling
  6. 3y agocarrierSource references dropped from crated functions
  7. 4y agocarrierInitial release with explicit-only crate packing

Frequently asked questions

What is the difference between carrier and contagionchannels?

Both compete on the same themes — r-package — within Infra & APIs. carrier and contagionchannels 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 carrier better than contagionchannels?

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

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

What are the best alternatives to contagionchannels?

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