workerpool
Offload tasks to a pool of workers on node.js and in the browser
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:src/generated/embeddedWorker.js | AI (source-diff): This is an auto-generated build artifact embedding a minified worker.js as a string — standard practice for workerpool's browser/worker instantiation pattern. Not malicious. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): workerpool's core purpose is spawning worker processes; child_process usage is fundamental and expected across all versions. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): requireFoolWebpack.js uses a static eval string to return the require function, preventing webpack bundling. Well-known pattern, not user-controlled input. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is workerpool's documented mechanism for deserializing and running user-provided functions in worker threads — core library feature, not a vulnerability. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of Sigstore provenance is not a disqualifying risk for this package. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 10.0.2 | 0 / 16 | |
| 10.0.1 | 0 / 16 | |
| 10.0.0 | 0 / 16 | |
| 9.3.4 | 0 / 16 | |
| 9.3.3 | 0 / 16 | |
| 9.3.2 | 0 / 16 | |
| 9.3.1 | 0 / 16 | |
| 9.3.0 | 0 / 16 | |
| 9.2.0 | 0 / 16 | |
| 9.1.3 | 0 / 16 | |
| 9.1.2 | 0 / 16 | |
| 9.1.1 | 0 / 15 | |
| 9.1.0 | 0 / 15 | |
| 9.0.4 | 0 / 15 | |
| 9.0.3 | 0 / 15 | |
| 9.0.2 | 0 / 15 | |
| 9.0.1 | 0 / 15 | |
| 9.0.0 | 0 / 15 | |
| 8.0.0 | 0 / 13 | |
| 7.0.0 | 0 / 13 | |
| 6.5.1 | 0 / 13 | |
| 6.5.0 | 0 / 13 | |
| 6.4.2 | 0 / 13 | |
| 6.4.1 | 0 / 13 | |
| 6.4.0 | 0 / 13 | |
| 6.3.1 | 0 / 13 | |
| 6.3.0 | 0 / 13 | |
| 6.2.1 | 0 / 13 | |
| 6.2.0 | 0 / 13 | |
| 6.1.5 | 0 / 13 | |
| 6.1.4 | 0 / 13 | |
| 6.1.3 | 0 / 13 | |
| 6.1.2 | 0 / 13 | |
| 6.1.1 | 0 / 13 | |
| 6.1.0 | 0 / 13 | |
| 6.0.4 | 0 / 10 | |
| 6.0.3 | 0 / 10 | |
| 6.0.2 | 0 / 10 | |
| 6.0.1 | 0 / 10 | |
| 6.0.0 | 0 / 10 | |
| 5.0.4 | 0 / 10 | |
| 5.0.3 | 0 / 10 | |
| 5.0.2 | 0 / 10 | |
| 5.0.1 | 0 / 9 | |
| 5.0.0 | 0 / 9 | |
| 4.0.0 | 1 / 9 | |
| 3.1.2 | 3 / 6 | |
| 3.1.1 | 1 / 6 | |
| 3.1.0 | 1 / 6 | |
| 3.0.0 | 1 / 6 | |
| 2.3.4 | 1 / 6 |
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.