esbuild-wasm MIT 88 versions

esbuild-wasm

npm Repository Homepage

The cross-platform WebAssembly binary for esbuild, a JavaScript bundler.

88

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

esbuild

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): The .node files are esbuild's compiled native binaries, a core part of its documented distribution. Expected for all esbuild-wasm versions.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed from evanw to GitHub Actions as part of CI/CD migration. SLSA provenance attestation confirms builds originate from the official evanw/esbuild repository.	ai	2026/04/24
maintainer-change	maintainer-takeover	AI (maintainer-change): esbuild migrated publishing to GitHub Actions CI/CD with SLSA provenance attestation. The repo URL remains evanw/esbuild; this is a documented supply chain improvement, not a hijack.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer 'esbuild' is the project's own npm org account, consistent with a legitimate organizational migration.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): evanw removed in favor of the project's org account and CI publishing; consistent with the documented migration pattern.	ai	2026/04/24
semgrep	semgrep:new-function-constructor	AI (semgrep): new Function() is esbuild-wasm's documented main-thread worker fallback for WASM execution. Stable pattern across all versions of this package.	ai	2026/04/24
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get() is part of the Go/WASM syscall/js runtime bridge in esbuild-wasm's browser bundle — standard boilerplate, not obfuscation.	ai	2026/04/23
semgrep	semgrep:child-process-spawn	AI (semgrep): spawn() is used to launch the esbuild service binary with --service and --ping flags — the canonical esbuild IPC protocol, not malicious.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): esbuild-wasm is a compiled WASM distribution package; no deps, minimal README, and no keywords are all expected for this type of artifact package.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): esbuild-wasm's Node.js API spawns the esbuild binary as a service process; child_process usage is documented and expected for this package.	ai	2026/04/23

Versions (showing 88 of 488)

Version	Deps	Published
0.5.6	0 / 0	2020-06-20
0.5.5	0 / 0	2020-06-20
0.5.4	0 / 0	2020-06-19
0.5.3	0 / 0	2020-06-12
0.5.2	0 / 0	2020-06-12
0.5.1	0 / 0	2020-06-11
0.5.0	0 / 0	2020-06-11
0.4.14	0 / 0	2020-06-11
0.4.13	0 / 0	2020-06-09
0.4.12	0 / 0	2020-06-09
0.4.11	0 / 0	2020-06-08
0.4.10	0 / 0	2020-06-08
0.4.9	0 / 0	2020-06-07
0.4.8	0 / 0	2020-06-05
0.4.7	0 / 0	2020-06-05
0.4.6	0 / 0	2020-06-05
0.4.5	0 / 0	2020-06-04
0.4.4	0 / 0	2020-06-03
0.4.3	0 / 0	2020-05-28
0.4.2	0 / 0	2020-05-26
0.4.1	0 / 0	2020-05-26
0.4.0	0 / 0	2020-05-26
0.3.9	0 / 0	2020-05-23
0.3.8	0 / 0	2020-05-22
0.3.7	0 / 0	2020-05-21
0.3.6	0 / 0	2020-05-21
0.3.5	0 / 0	2020-05-18
0.3.4	0 / 0	2020-05-18
0.3.3	0 / 0	2020-05-17
0.3.2	0 / 0	2020-05-14
0.3.1	0 / 0	2020-05-14
0.3.0	0 / 0	2020-05-13
0.2.12	0 / 0	2020-05-13
0.2.11	0 / 0	2020-05-10
0.2.10	0 / 0	2020-05-09
0.2.9	0 / 0	2020-05-08
0.2.8	0 / 0	2020-05-07
0.2.7	0 / 0	2020-05-07
0.2.6	0 / 0	2020-05-06
0.2.5	0 / 0	2020-05-06
0.2.4	0 / 0	2020-05-06
0.2.3	0 / 0	2020-05-06
0.2.2	0 / 0	2020-05-06
0.2.1	0 / 0	2020-05-05
0.2.0	0 / 0	2020-05-05
0.1.26	0 / 0	2020-05-05
0.1.25	0 / 0	2020-05-05
0.1.24	0 / 0	2020-05-04
0.1.23	0 / 0	2020-05-03
0.1.22	0 / 0	2020-05-03
0.1.21	0 / 0	2020-05-02
0.1.20	0 / 0	2020-05-02
0.1.19	0 / 0	2020-05-01
0.1.18	0 / 0	2020-04-30
0.1.17	0 / 0	2020-04-29
0.1.16	0 / 0	2020-04-23
0.1.15	0 / 0	2020-04-22
0.1.14	0 / 0	2020-04-21
0.1.13	0 / 0	2020-04-20
0.1.12	0 / 0	2020-04-19
0.1.11	0 / 0	2020-04-19
0.1.10	0 / 0	2020-04-18
0.1.9	0 / 0	2020-04-18
0.1.8	0 / 0	2020-04-16
0.1.7	0 / 0	2020-04-16
0.1.6	0 / 0	2020-04-16
0.1.5	0 / 0	2020-04-15
0.1.4	0 / 0	2020-04-15
0.1.3	0 / 0	2020-04-13
0.1.2	0 / 0	2020-04-13
0.1.1	0 / 0	2020-04-13
0.1.0	0 / 0	2020-04-13
0.0.16	0 / 0	2020-04-09
0.0.15	0 / 0	2020-04-07
0.0.14	0 / 0	2020-04-07
0.0.13	0 / 0	2020-04-07
0.0.12	0 / 0	2020-04-07
0.0.11	0 / 0	2020-04-07
0.0.10	0 / 0	2020-03-31
0.0.9	0 / 0	2020-02-18
0.0.8	0 / 0	2020-02-17
0.0.7	0 / 0	2020-02-16
0.0.6	0 / 0	2020-01-26
0.0.5	0 / 0	2020-01-21
0.0.4	0 / 0	2020-01-19
0.0.3	0 / 0	2020-01-15
0.0.2	0 / 0	2020-01-13
0.0.1	0 / 0	2020-01-01

v0.5.6

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.5.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.5.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.5.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.5.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.5.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.5.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.4.14

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

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

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

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

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

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

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

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

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.4.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.4.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.4.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.4.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.4.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.4.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.3.9

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

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

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

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.3.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.3.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.3.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.3.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.3.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.3.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.2.12

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

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

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

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

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

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

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.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.2.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.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.26

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v0.0.16

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

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

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

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

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

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

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

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

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

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

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