@parcel/workers
Blazing fast, zero configuration web application bundler
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): WorkerFarm dynamically requires a configurable worker module path — this is the core design of a worker farm, not a malicious pattern. Stable across all versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in cpuCount.js to detect available CPU cores — a standard, benign system introspection pattern for a build tool worker farm. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in ProcessChild.js is the IPC serialization mechanism for passing structured data between worker processes — expected and documented behavior. | ai | |
| phantom-deps | phantom-dep:@parcel/utils | AI (phantom-deps): @parcel/utils is explicitly listed in package.json dependencies and is a sibling package in the same org scope; phantom-dep detection is a false positive here. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 2.16.4 | 6 / 0 | |
| 2.16.3 | 6 / 0 | |
| 2.16.2 | 6 / 0 | |
| 2.16.1 | 6 / 0 | |
| 2.16.0 | 6 / 0 | |
| 2.15.4 | 6 / 0 | |
| 2.15.3 | 6 / 0 | |
| 2.15.2 | 6 / 0 | |
| 2.15.1 | 6 / 0 | |
| 2.15.0 | 6 / 0 | |
| 2.14.4 | 6 / 0 | |
| 2.14.3 | 6 / 0 | |
| 2.14.2 | 6 / 0 | |
| 2.14.1 | 6 / 0 | |
| 2.14.0 | 6 / 0 | |
| 2.13.3 | 6 / 0 | |
| 2.13.2 | 6 / 0 | |
| 2.13.1 | 6 / 0 | |
| 2.13.0 | 6 / 0 | |
| 2.12.0 | 6 / 0 | |
| 2.11.0 | 6 / 0 | |
| 2.10.3 | 6 / 0 | |
| 2.10.2 | 6 / 0 | |
| 2.10.1 | 6 / 0 | |
| 2.10.0 | 6 / 0 | |
| 2.9.3 | 6 / 0 | |
| 2.9.2 | 6 / 0 | |
| 2.9.1 | 6 / 0 | |
| 2.9.0 | 6 / 0 | |
| 2.8.3 | 6 / 0 | |
| 2.8.2 | 6 / 0 | |
| 2.8.1 | 6 / 0 | |
| 2.8.0 | 6 / 0 | |
| 2.7.0 | 6 / 0 | |
| 2.6.2 | 6 / 0 | |
| 2.6.1 | 6 / 0 | |
| 2.6.0 | 6 / 0 | |
| 2.5.0 | 6 / 0 | |
| 2.4.1 | 6 / 0 | |
| 2.4.0 | 6 / 0 | |
| 2.3.2 | 6 / 0 | |
| 2.3.1 | 6 / 0 | |
| 2.3.0 | 6 / 0 | |
| 2.2.1 | 6 / 0 | |
| 2.2.0 | 6 / 0 | |
| 2.1.1 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.1 | 6 / 0 | |
| 2.0.0 | 6 / 0 | |
| 1.11.0 | 2 / 1 |
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.