mrkeyoor.comAsk

ramda/ramdatested 03 Oct 2026commit f6fd605

ramda review

Use Ramda when currying and data-last composition make your team's transformations easier to review.

  • Install 30 s
  • Build 11 s
1,224/1,224tests passed
  • 766 packages
Dev Toolsevaluationupdated 01 Nov 2026
+3stars / 7d

Choose Ramda when automatic currying and data-last composition make your team's JavaScript transformations easier to review. Ramda functions are automatically curried, and their input data generally comes last. The checkout at f6fd605 declares version 0.32.0. Our stored October 3, 2026 run completed installation, build and test commands successfully; it did not establish application performance, production bundle size, TypeScript compatibility or Deno compatibility.

Verdict

Use Ramda when currying and data-last composition make your team's transformations easier to review. The dated sandbox run supports successful contributor commands, with explicit limits on the stored test counts. Before adopting it, check a representative pipeline, inspect production bundle output and obtain a current dependency audit. The conflicting audit evidence prevents a security conclusion.

We ran it

Lab card: what happened when we ran ramda
Lab card from our sandbox run
Screenshot of ramda (ramdajs.com)
ramdajs.com
Install✓ · 30s766 packages · 155 MB
Build✓ · 11s
Tests✓ · 11s1224 passed · 0 failed of 1224 (mocha)
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo712 files~25,921 lines of source · 1.6 MB · 2 CI workflows · tests dir

Answers from our run

Does ramda build from source?

Dependencies installed in 30 seconds (766 packages), and the build succeeded in 11 seconds. We cloned commit f6fd605 into a clean Debian container with 3 CPUs and no project-specific setup.

Do ramda's tests pass?

Yes. The project's own test command finished in 11 seconds and reported 1224 passed, 0 failed (mocha).

Does ramda have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use ramda?

Teams whose reviewers find native JavaScript transformations easier to follow.

What are the alternatives to ramda?

Remeda, Lodash. Use Ramda when currying and data-last composition make your team's transformations easier to review.

Setup4/5The contributor installation, build and test commands succeeded. Differences between stored dependency measurements and installation output remain unresolved.
Docs4/5The supplied README explains installation, imports, builds and tests, but its Deno example targets v0.27.2 rather than the checkout's declared 0.32.0. This assesses that guidance, not the full API reference.
Community4/5Last push on 2026-10-03 and 24,051 stars.Editor’s note: The supplied evidence does not establish community responsiveness or provide enough verified activity history to support a numerical judgment.
Maturity3/5Latest release v0.32.0 on 2025-10-10 (pre-1.0), repository created 2013-06-21 and its test suite passed in our sandbox (1,224 of 1,224 passed).Editor’s note: Successful contributor commands and stored parser counts do not establish production maturity, exhaustive coverage or application suitability.

How we score

Discussed on

  1. hnRamda – A practical functional library for Javascript80 points
  2. hnRamda: A practical functional library for JavaScript programmers66 points
  3. hnRamda-cli, a jq-like CLI tool for processing data with functional pipelines36 points
  4. hnVulnerabilities in the hidden magic of Lodash, Ramda and Underscore6 points
  5. hnWhy Ramda?5 points

Who it’s for

JavaScript teams comfortable reviewing curried functions and composed transformations.
Maintainers evaluating the contributor checkout at f6fd605, which declares version 0.32.0.
Developers working with ordinary JavaScript objects and arrays who want to prepare operations before supplying their data.

Who it’s NOT for

Teams whose reviewers find native JavaScript transformations easier to follow.
Browser projects requiring a measured production bundle cost before adoption; this run provides none.
Teams treating a successful contributor test command as proof of application compatibility.
Readers seeking a security assessment; the stored audit summary and installation output conflict.

Setup reality

The stored October 3, 2026 run at f6fd605 used Node 22, 3 CPUs and 8 GB of memory. The harness records installation at 30 seconds, build at 11 seconds and the complete test command at 11 seconds. Each returned exit code 0 without a recorded timeout. No new execution occurred for this correction.

The stored parser summaries report 1,224 passed, 0 failed and 1,224 total tests. These counts do not establish exhaustive unique coverage. The raw Mocha footer reports 1,224 passing in 1 second, a narrower duration than the complete command's 11 seconds.

The stored dependency summary records 766 packages and 155 MB. Installation output contains different package figures that remain unreconciled. The stored audit summary records 0 advisories, but installation output contains a conflicting vulnerability report. Scan coverage is unknown because scannedPackages is absent.

Should your team use Ramda?

Choose Ramda when its calling conventions make transformations easier for your team to review. Ramda functions are automatically curried, and their input data generally comes last. This lets developers prepare an operation before supplying its data. Try that style on a representative transformation before adopting it across a codebase.

The README at f6fd605 describes plain JavaScript objects and arrays as its basic data structures. It promotes immutable, side-effect-free programming but says it does not enforce that style. Review callbacks and application code for mutation rather than assuming the library prevents it.

What the stored run establishes

Our run on October 3, 2026, at commit f6fd605 recorded successful installation, build and test commands. This correction uses that existing record; no new execution occurred. The sandbox record identifies Node 22, 3 CPUs and 8 GB of memory.

Installation took 30 seconds, build took 11 seconds and the complete test command took 11 seconds. Each returned exit code 0 without a recorded timeout. The build output shows Babel compiling CommonJS and ES module outputs.

The stored parser summaries report 1,224 passed, 0 failed and 1,224 total tests. They do not establish exhaustive unique test coverage. The raw Mocha footer reports 1,224 passing in 1 second. Its repeated appearance in the supplied tail does not represent additional tests, and its duration does not replace the complete command's 11 seconds.

The package metadata defines the test command as parallel execution of spec and lint. Its successful exit records that command's outcome in this sandbox. It does not establish browser execution, application deployment, runtime speed or compatibility with your pipelines. The supplied run includes no production bundle measurement or representative application workload.

The MrKeyoor testing methodology explains command recording and measurement limits. That supplied page describes the current procedure; it does not establish which procedure version governed this older run.

The audit evidence remains unresolved

The stored audit summary records 0 advisories. Installation output contains a conflicting vulnerability report, so the stored zero cannot support a claim that the checkout has no known vulnerabilities. Neither record resolves the discrepancy, and the installation report does not replace the stored measurement.

Scan coverage is unknown because scannedPackages is absent. Package figures printed during installation do not establish that missing coverage. These records concern dependency advisories, not a security review of Ramda. Obtain a current audit and inspect the affected dependency paths before drawing a security conclusion.

The stored dependency summary records 766 packages and 155 MB. Installation output contains different package figures that remain unreconciled. The manifest declares no runtime dependencies, so the contributor checkout footprint does not establish the production cost of importing Ramda.

Check imports and your target environment

The checkout at f6fd605 declares version 0.32.0. Its manifest defines separate require and import entry points. That establishes the declared package layout, not successful imports in your application or equivalence between this checkout and the release tag. The README also warns that versions after 0.25 have no default export.

The README says destructuring imports does not necessarily prevent inclusion of the entire library. It describes per-function imports, partial builds and bundler-specific approaches. Inspect your production output before making a bundle-size decision.

The README's Deno example targets v0.27.2 rather than the checkout's declared 0.32.0. This run did not test that path. Its TypeScript typings link likewise does not establish compatibility with your curried calls. Check representative transformations in the environment you intend to ship.

Alternatives depend on the requirement

Remeda supports both data-first and data-last calls and advertises first-class TypeScript support. Its primary README supports evaluating it when types and both calling styles are requirements. The supplied run did not test Remeda or establish migration compatibility.

Lodash's FP build provides immutable, automatically curried, iteratee-first, data-last methods. The Lodash README supports considering lodash/fp for functional utilities. Choosing Lodash therefore does not require giving up currying. Neither alternative is established here as a drop-in replacement.

How to read the ratings

The numerical ratings assess only the contributor setup path and the supplied README guidance. On this editorial scale, 1 means a documented obstacle prevents the evaluated task; 2 means substantial friction; 3 means usable with unresolved practical limits; 4 means the evaluated path works with a concrete caveat; and 5 requires evidence that the dimension's stated criterion is fully met. These are judgments, not benchmarks.

Setup ease is 4 because the contributor commands succeeded, although the installation records remain unreconciled. Documentation is 4 because the README supplies installation, import, build and test guidance, with a Deno example targeting an older version. This documentation judgment does not assess the full API reference.

Community and maturity are unassessed and have no numerical ratings. The supplied extracts do not establish community responsiveness or production maturity. Successful contributor commands and parser counts cannot establish either dimension.

Alternatives

ProjectWhat it isPick it when
RemedaA utility library designed for TypeScript with data-first and data-last calls.Evaluate it when TypeScript support and both calling styles are requirements; verify your actual pipelines before migrating.
Lodash gh↗A JavaScript utility library whose FP build provides automatically curried, data-last methods.Evaluate lodash/fp when its functional utilities fit your application; verify behavior before treating it as a replacement.

What people are saying

  1. [velocity-scout] ramda/ramda

Sources

  1. Ramda README
  2. Ramda package metadata at tested commit
  3. Ramda v0.32.0 release
  4. Ramda 0.32.0 upgrade guide
  5. Deno release tracking issue
  6. Ramda scan transducer issue
  7. Ramda versioning discussion

More dev tools reviews