ramda — Greenflagged

A practical functional library for JavaScript programmers.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

crosseyedavidchambersranebuzzdecafescott-christopheraromanokedashoebradcomp

Keywords

ramdafunctionalutilsutilitiestoolkitfptacitpoint-freecurriedpurefantasy-land

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:docs/scripts/underscore-min.js	AI (source-diff): Standard minified Underscore.js 1.5.2 bundled in docs folder as a documentation dependency; not malicious.	ai	2026/04/24
source-diff	net-exec-file:docs/scripts/underscore-min.js	AI (source-diff): Minified Underscore.js in docs folder; network+exec pattern is normal for a utility library, not a dropper.	ai	2026/04/24
source-diff	net-exec-file:lib/test/expect.js	AI (source-diff): Well-known expect.js test assertion library bundled in test directory; not malicious.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Very old version (~2014) when gitHead tracking was inconsistent; publisher is a listed contributor with long history on this package.	ai	2026/04/24
source-diff	net-exec-file:tmp-test-bundle.js	AI (source-diff): Browserify test bundle of Ramda itself accidentally included in package; not malicious code. Standard bundler boilerplate triggers the net+exec heuristic.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from accidentally included test bundle (tmp-test-bundle.js) and IDE config (.idea/workspace.xml); no malicious payload.	ai	2026/04/24
semgrep	semgrep:new-function-constructor	AI (semgrep): Ramda uses new Function() to build optimized curried functions from internally-constructed string templates — a well-known intentional pattern in functional JS libraries, not a security risk.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process usage is in Gruntfile.js (dev tooling only) for code coverage tasks; not in runtime code and not accessible to package consumers.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): crosseye (Scott Sauyet) is a named author/contributor in package.json and a long-standing Ramda maintainer; publisher rotation is expected for this community-maintained project.	ai	2026/04/24
source-diff	large-new-source-files	AI (source-diff): 0.26.0 added ES module output (es/ directory), producing ~346 new files — one per function. This is consistent with the added build:mjs/build:es scripts and documented ES module support.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Ramda is a community project with multiple known maintainers; adding contributors is normal and expected for this package.	ai	2026/04/24

Versions (showing 60 of 60)

Version	Deps	Published
0.32.0	0 / 31	2025-10-10
0.31.3	0 / 31	2025-06-22
0.31.2	0 / 31	2025-06-22
0.31.1	0 / 31	2025-06-22
0.31.0	0 / 31	2025-06-22
0.30.1	0 / 31	2024-06-02
0.30.0	0 / 31	2024-04-28
0.29.1	0 / 32	2023-10-05
0.29.0	0 / 32	2023-04-02
0.28.0	0 / 29	2022-01-16
0.27.2	0 / 27	2022-01-11
0.27.1	0 / 27	2020-07-30
0.27.0	0 / 27	2020-02-02
0.26.1	0 / 26	2018-11-28
0.26.0	0 / 26	2018-11-18
0.25.0	0 / 24	2017-10-09
0.24.1	0 / 22	2017-06-02
0.24.0	0 / 22	2017-05-27
0.23.0	0 / 22	2016-12-28
0.22.1	0 / 21	2016-08-07
0.22.0	0 / 21	2016-08-04
0.21.0	0 / 20	2016-04-09
0.20.1	0 / 20	2016-03-29
0.20.0	0 / 20	2016-03-26
0.19.1	0 / 19	2016-01-04
0.19.0	0 / 19	2015-12-22
0.18.0	0 / 20	2015-10-11
0.17.1	0 / 19	2015-07-21
0.17.0	0 / 19	2015-07-20
0.16.0	0 / 19	2015-07-13
0.15.1	0 / 19	2015-06-21
0.15.0	0 / 20	2015-06-14
0.14.0	0 / 37	2015-05-11
0.13.0	0 / 37	2015-03-22
0.12.0	0 / 37	2015-03-21
0.11.0	0 / 38	2015-03-08
0.10.0	0 / 37	2015-02-15
0.9.1	0 / 37	2015-01-28
0.9.0	0 / 33	2015-01-25
0.8.0	0 / 21	2014-11-19
0.7.2	0 / 19	2014-10-24
0.7.1	0 / 19	2014-10-23
0.7.0	0 / 19	2014-10-23
0.6.0	0 / 21	2014-10-04
0.5.0	0 / 23	2014-09-16
0.4.3	0 / 18	2014-09-01
0.4.2	0 / 18	2014-09-01
0.4.1	0 / 18	2014-08-31
0.4.0	0 / 18	2014-08-28
0.3.0	0 / 14	2014-08-10
0.2.4	0 / 14	2014-07-18
0.2.3	0 / 13	2014-07-10
0.2.2	0 / 9	2014-06-30
0.2.1	0 / 9	2014-06-28
0.2.0	0 / 9	2014-06-28
0.1.5	0 / 8	2014-06-11
0.1.4	0 / 0	2014-06-11
0.1.2	0 / 8	2014-05-18
0.1.1	0 / 8	2014-05-18
0.1.0	0 / 8	2014-05-16

v0.29.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: crosseye → kedashoe (on 2023-04-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-02. This could indicate a legitimate maintainer transition or an account compromise.

v0.28.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → crosseye (on 2022-01-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-01-16. This could indicate a legitimate maintainer transition or an account compromise.

v0.27.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.1

2 findings

HIGH Publisher changed: crosseye → davidchambers (on 2020-07-30) provenance

This version was published by a different npm account than previous versions on 2020-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.0

2 findings

HIGH Publisher changed: kedashoe → crosseye (on 2018-11-18) provenance

This version was published by a different npm account than previous versions on 2018-11-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: scott-christopher → kedashoe (on 2017-05-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-27. This could indicate a legitimate maintainer transition or an account compromise.

v0.23.0

3 findings

HIGH New file with network + code execution: tmp-test-bundle.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: buzzdecafe → scott-christopher (on 2016-12-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-28. This could indicate a legitimate maintainer transition or an account compromise.

v0.22.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: scott-christopher → buzzdecafe (on 2016-08-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-08-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.22.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aromano → scott-christopher (on 2016-08-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-08-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.21.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → aromano (on 2016-04-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.20.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → aromano (on 2016-03-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-29. This could indicate a legitimate maintainer transition or an account compromise.

v0.20.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → buzzdecafe (on 2016-03-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-26. This could indicate a legitimate maintainer transition or an account compromise.

v0.19.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → buzzdecafe (on 2015-05-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-05-11. This could indicate a legitimate maintainer transition or an account compromise.

v0.13.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: buzzdecafe → davidchambers (on 2015-03-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-03-22. This could indicate a legitimate maintainer transition or an account compromise.

v0.12.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: buzzdecafe.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → buzzdecafe (on 2015-03-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-03-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: buzzdecafe → davidchambers (on 2014-11-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-11-19. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: buzzdecafe.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidchambers → buzzdecafe (on 2014-10-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-10-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: buzzdecafe → davidchambers (on 2014-10-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-10-23. This could indicate a legitimate maintainer transition or an account compromise.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: crosseye → buzzdecafe (on 2014-09-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-16. This could indicate a legitimate maintainer transition or an account compromise.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

5 findings

HIGH New obfuscated file: docs/scripts/underscore-min.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: docs/scripts/underscore-min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: lib/test/expect.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: buzzdecafe → crosseye (on 2014-09-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-01. This could indicate a legitimate maintainer transition or an account compromise.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: crosseye → buzzdecafe (on 2014-07-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-07-18. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.