piscina
A fast, efficient Node.js Worker Thread Pool implementation
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (rafaelgss, qard, metcoder95) are known Node.js ecosystem contributors; this is a legitimate org-level maintainer expansion, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): rafaelgss is a known Node.js core contributor with strong track record; the piscinajs org maintainer transition is publicly documented and legitimate. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() wraps a static string literal to prevent TS/CJS compiler from transforming dynamic import(). This is a standard, safe workaround for ESM interop in CommonJS — not user-controlled input. | ai | |
| dependencies | unvetted-dep:nice-napi | AI (dependencies): nice-napi is an optional dependency for thread priority management, well-known in the Node.js native addon ecosystem and appropriate for a worker pool library. | ai | |
| dependencies | unvetted-dep:eventemitter-asyncresource | AI (dependencies): eventemitter-asyncresource is a standard Node.js async context tracking utility, appropriate for a worker thread pool implementation. | ai | |
| dependencies | unvetted-dep:hdr-histogram-percentiles-obj | AI (dependencies): hdr-histogram-percentiles-obj is a utility for HDR histogram metrics, appropriate for piscina's performance monitoring features. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function used solely to wrap dynamic import() for CJS/ESM interop — a standard, safe pattern in the Node.js ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 5.1.4 | 0 / 10 | |
| 5.1.3 | 0 / 10 | |
| 5.1.2 | 0 / 11 | |
| 5.1.1 | 0 / 11 | |
| 5.1.0 | 0 / 11 | |
| 5.0.0 | 0 / 11 | |
| 4.9.2 | 0 / 13 | |
| 4.9.1 | 0 / 13 | |
| 4.9.0 | 0 / 13 | |
| 4.8.0 | 0 / 13 | |
| 4.7.0 | 0 / 13 | |
| 4.6.1 | 0 / 13 | |
| 4.6.0 | 0 / 13 | |
| 4.5.1 | 0 / 13 | |
| 4.5.0 | 0 / 13 | |
| 4.4.0 | 0 / 11 | |
| 4.3.2 | 0 / 11 | |
| 4.3.1 | 0 / 11 | |
| 4.3.0 | 0 / 11 | |
| 4.2.1 | 3 / 11 | |
| 4.2.0 | 3 / 11 | |
| 4.1.0 | 4 / 11 | |
| 4.0.0 | 4 / 11 | |
| 3.2.0 | 4 / 11 | |
| 3.1.0 | 4 / 11 | |
| 3.0.0 | 4 / 11 | |
| 2.2.0 | 4 / 10 | |
| 2.1.0 | 4 / 10 | |
| 2.0.0 | 4 / 10 | |
| 1.6.3 | 4 / 10 | |
| 1.6.2 | 4 / 10 | |
| 1.6.1 | 4 / 10 | |
| 1.6.0 | 4 / 10 | |
| 1.5.1 | 3 / 10 | |
| 1.5.0 | 3 / 9 | |
| 1.4.0 | 3 / 9 | |
| 1.3.0 | 3 / 9 | |
| 1.1.0 | 2 / 8 | |
| 1.0.0 | 2 / 8 |
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-08-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-06-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.