← Back to home
Comparison · Analytics

EDIutils vs webchem

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

Shared themes:ropensci

EDIutils vs webchem: at a glance

FeatureEDIutilswebchem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesropensci, r-package, api-client, ecologycheminformatics, web-apis, data-access, ropensci
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is EDIutils?

The EDI data client is being dragged through its repository's identity-system migration.

EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.

Read the full EDIutils trajectory →

What is webchem?

Adding chemical databases with one hand while public ones close programmatic access with the other.

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

Read the full webchem trajectory →

EDIutils vs webchem: editorial side-by-side

E
EDIutils
ANALYTICS
0.0

The EDI data client is being dragged through its repository's identity-system migration.

◆ Current state

EDIutils is the R client for the Environmental Data Initiative repository. The last two releases are both consequences of changes at EDI rather than in the package: 2.0.0 rewired authentication for the new EDI Identity and Access Manager and made Distinguished Names defunct in favour of EDI-IDs, and 2.1.0 handles the deprecation of the old auth token. Earlier releases were small bug fixes against repository outages and endpoint changes.

◆ Where it's heading

This is a client whose roadmap belongs to its server. Every meaningful release tracks something EDI changed — a deprecated endpoint, a resource outage breaking CRAN checks, and now a whole identity system — and the package's job is to absorb the churn while keeping the R interface stable. The 2.0.0 break was handled by pointing users at where to find their new EDI-ID rather than by papering over the change.

◆ Prediction

Expect continued follow-through on the IAM migration as the old auth token is fully retired, and further releases keyed to EDI service changes rather than to new client features.

W
webchem
ANALYTICS
0.0

Adding chemical databases with one hand while public ones close programmatic access with the other.

◆ Current state

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

◆ Where it's heading

Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.

◆ Prediction

Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.

Alternatives to EDIutils and webchem

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 EDIutils or webchem.

See all EDIutils alternatives → · See all webchem alternatives →

Recent activity from EDIutils and webchem

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

  1. 3mo agoEDIutilsGraceful handling for the deprecated auth token
  2. 7mo agoEDIutilsEDI-IDs replace Distinguished Names as authentication moves to IAM
  3. 1y agowebchemRepairs broken URLs; ChemSpider check now needs a key
  4. 2y agoEDIutilsDeprecated archive endpoint fixed
  5. 3y agowebchemChemIDplus and PAN queries removed as sources shut down
  6. 3y agowebchemAdds ChEMBL access for bioactive compound data
  7. 3y agoEDIutilsCRAN check fixed after EDI repository outage
  8. 4y agoEDIutilsCharacter encoding bug fixed in a dependency path
  9. 4y agowebchemcir_query() returns a tibble, a breaking change
  10. 4y agowebchemAdds Mol structure export; aw_query renamed to bcpc_query
  11. 5y agowebchemFetches LIPID MAPS and SwissLipids identifiers from Wikidata

Frequently asked questions

What is the difference between EDIutils and webchem?

Both compete on the same themes — ropensci — within Analytics. EDIutils and webchem 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 EDIutils better than webchem?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EDIutils and webchem 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 Analytics products to evaluate alongside.

What are the best alternatives to EDIutils?

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

What are the best alternatives to webchem?

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