Bump js-sys from 0.3.85 to 0.3.103

[dependabot]

Bumps js-sys from 0.3.85 to 0.3.103.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Low Risk
Lockfile-only dependency refresh for WASM/js-sys; main risk is regressions in WASM builds or getrandom on the browser target, not runtime logic in this repo.

Overview
Updates the lockfile for js-sys 0.3.85 → 0.3.103 (Dependabot). The newer crate drops once_cell and adds cfg-if and futures-util, which pulls in futures-core, futures-task, pin-project-lite, and slab as transitive dependencies.

The same resolution bumps the wasm-bindgen stack from 0.2.108 to 0.2.126 (wasm-bindgen, macro crates, and shared). getrandom’s wasm path still depends on js-sys, so this affects WASM/randomness bindings indirectly.

No application source changes—only Cargo.lock.

^{Reviewed by Cursor Bugbot for commit a2c2b96. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​wasm-bindgen@​0.2.108 ⏵ 0.2.126
	cargo/​js-sys@​0.3.85 ⏵ 0.3.103	-16		+2

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Install-time scripts: cargo js-sys Install script: Package overview Source: undefined From: Cargo.lock → cargo/js-sys@0.3.103 ℹ Read more on: This package | This alert | What is an install script? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/js-sys@0.3.103. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report