worker-farm MIT 22 versions

worker-farm

npm Repository Homepage

Distribute processing tasks to child processes with an über-simple API and baked-in durability & custom concurrency options.

22

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

amasadrvagg

Keywords

workerchildprocessingfarm

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): worker-farm is a legitimate, long-established package (4861 days old, 22 versions) by trusted publisher rvagg. The 0.0.0 version is simply its initial release, not a malicious throwaway.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): rvagg (Rod Vagg) is the original and canonical author per package.json and the GitHub repo URL; the change from amasad reflects a legitimate ownership transfer back to the original author.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core mechanism of worker-farm: child processes load the user-specified worker module by design. This is intentional and documented behavior.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): worker-farm's entire purpose is to fork child processes; child_process usage is fundamental and expected for this package.	ai	2026/04/23

Versions (showing 22 of 22)

Version	Deps	Published
1.7.0	1 / 1	2019-05-03
1.6.0	1 / 1	2018-03-09
1.5.4	2 / 1	2018-02-26
1.5.3	2 / 1	2018-02-26
1.5.2	2 / 1	2017-11-16
1.5.1	2 / 1	2017-10-30
1.5.0	2 / 1	2017-08-14
1.4.1	2 / 1	2017-06-30
1.4.0	2 / 1	2017-06-30
1.3.1	2 / 1	2015-05-21
1.3.0	2 / 1	2015-05-11
1.2.0	2 / 1	2015-02-04
1.1.0	2 / 1	2014-11-17
1.0.1	2 / 1	2014-08-16
1.0.0	2 / 1	2014-08-16
0.3.1	2 / 1	2013-09-19
0.3.0	2 / 1	2013-09-17
0.2.1	2 / 1	2013-08-29
0.2.0	2 / 1	2013-08-29
0.1.0	1 / 1	2013-08-29
0.0.1	0 / 1	2013-01-09
0.0.0	0 / 1	2013-01-01

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

2 findings

HIGH Publisher changed: amasad → rvagg (on 2017-06-30) provenance

This version was published by a different npm account than previous versions on 2017-06-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.

v1.4.0

2 findings

HIGH Publisher changed: amasad → rvagg (on 2017-06-30) provenance

This version was published by a different npm account than previous versions on 2017-06-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.

v1.3.1

2 findings

HIGH Publisher changed: rvagg → amasad (on 2015-05-21) provenance

This version was published by a different npm account than previous versions on 2015-05-21. 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.

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.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.1

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.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.1

1 finding

LOW No provenance attestation provenance

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

v0.0.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.