Bump core-js from 3.32.1 to 3.47.0

[dependabot]

Bumps core-js from 3.32.1 to 3.47.0.

Changelog

Sourced from core-js's changelog.

3.47.0 - 2025.11.18

• Changes v3.46.0...v3.47.0 (117 commits)
• JSON.parse source text access proposal :
  • Built-ins:
    • JSON.isRawJSON
    • JSON.parse
    • JSON.rawJSON
    • JSON.stringify
  • Moved to stable ES, November 2025 TC39 meeting
  • Added es. namespace modules, /es/ and /stable/ namespaces entries
  • Reworked JSON.stringify internals
• Iterator sequencing proposal:
  • Built-ins:
    • Iterator.concat
  • Moved to stable ES, November 2025 TC39 meeting
  • Added es. namespace modules, /es/ and /stable/ namespaces entries
• Joint iteration proposal:
  • Built-ins:
    • Iterator.zip
    • Iterator.zipKeyed
  • Moved to stage 3, November 2025 TC39 meeting
  • Added /actual/ namespace entries, unconditional forced replacement changed to feature detection
• Fixed increasing .size in URLSearchParams.prototype.append polyfill in IE8-
• Compat data improvements:
  • Iterator.concat marked as shipped in FF147
  • Map upsert proposal features marked as shipped in Safari 26.2
  • Math.sumPrecise marked as shipped in Safari 26.2
  • Uint8Array.{ fromBase64, prototype.setFromBase64 } marked as fixed in Safari 26.2
  • Missed Explicit Resource Management features added in Bun 1.3.0
  • Added Oculus Quest Browser 41 compat data mapping
  • Added Electron 40 compat data mapping

3.46.0 - 2025.10.09

• Changes v3.45.1...v3.46.0 (116 commits)
• Map upsert stage 3 proposal:
  • Fixed a FF WeakMap.prototype.getOrInsertComputed bug with callback calling before validation a key
• Iterator chunking proposal:
  • Built-ins:
    • Iterator.prototype.chunks
    • Iterator.prototype.windows
  • Moved to stage 2.7, September 2025 TC39 meeting
  • Iterator.prototype.sliding method replaced with an extra parameter of Iterator.prototype.windows method, [tc39/proposal-iterator-chunking/#24](tc39/proposal-iterator-chunking#24), [tc39/proposal-iterator-chunking/#26](tc39/proposal-iterator-chunking#26)
• Fixed Iterator.zip and Iterator.zipKeyed behavior with mode: 'longest' option, #1469, thanks @​lionel-rowe
• Fixed work of Object.groupBy and Iterator.zipKeyed together with Symbol polyfill - some cases of symbol keys on result null-prototype object were able to leak out to for-in
• Compat data improvements:
  • Map upsert proposal features marked as shipped from FF144
  • Added Node 25.0 compat data mapping
  • Added Deno 2.5 compat data mapping
  • Updated Electron 39 compat data mapping
  • Updated Opera 121+ compat data mapping

... (truncated)

Commits

• c1d2c7e v3.47.0
• 400f00e move JSON.parse source text access to stable ES
• 2b383e9 move joint iteration to stage 3
• 21f984c move Iterator sequencing proposal to stable ES
• 6add4cd add explicit "sideEffects": true to core-js and core-js-bundle packages
• 0f6c98d update eslint-plugin-unicorn
• fe04540 fix increasing .size in URLSearchParams.prototype.append polyfill in IE8-
• 98d9dc4 v3.46.0
• 38420bd add homepage field to package.jsons
• a7aee4c some fixes
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	core-js@​3.32.1 ⏵ 3.47.0	+1		+1	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm core-js is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, non-malicious implementation of multiple Array prototype iteration methods from core-js. It reads input from the provided array-like object and a user-provided callback, and writes results into a created target array where appropriate. There is no evident data exfiltration, backdoor, or other malicious activity. Overall security risk appears low to moderate in isolation, with no suspicious behavior detected in this fragment. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm core-js is 100.0% likely to have a medium risk anomaly Notes: The code constitutes a standards-compliant polyfill/compatibility patch for RegExp/String.prototype.replace with robust handling of named groups and replacer semantics. No evidence of malware, exfiltration, or sensitive data leakage. The risk profile is typical for polyfills in open-source libraries and is acceptable when used in trusted contexts, albeit with standard caution about using third-party dependencies in supply chains. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm core-js is 100.0% likely to have a medium risk anomaly Notes: The code implements a targeted safety polyfill for Uint8Array.prototype.setFromBase64 to support base64 decoding into typed arrays. It includes environment feature checks and uses internal decoding helpers to fill the array and report read/written counts. No malicious activity detected; the flow is confined to in-memory decoding and prototype augmentation. This appears to be a legitimate compatibility helper rather than malware. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm core-js is 100.0% likely to have a medium risk anomaly Notes: The fragment implements a conventional abstract AsyncIterator polyfill pattern. It prevents direct construction, attaches type metadata, and exposes AsyncIteratorConstructor globally in a controlled manner. There are no signs of data exfiltration, external I/O, or hidden behavior. Overall security risk is low, malware likelihood is negligible in this fragment, and the code aligns with legitimate library usage (e.g., core-js style shims). Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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