Skip to content

build(deps): bump @tootallnate/once and electron-builder#633

Open
dependabot[bot] wants to merge 1 commit intodevelopfrom
dependabot/npm_and_yarn/multi-3ffb4d349a
Open

build(deps): bump @tootallnate/once and electron-builder#633
dependabot[bot] wants to merge 1 commit intodevelopfrom
dependabot/npm_and_yarn/multi-3ffb4d349a

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 5, 2026

Removes @tootallnate/once. It's no longer used after updating ancestor dependency electron-builder. These dependencies need to be updated together.

Removes @tootallnate/once

Updates electron-builder from 25.1.8 to 26.8.1

Release notes

Sourced from electron-builder's releases.

electron-builder@26.8.1

What's Changed

Full Changelog: https://github.com/electron-userland/electron-builder/compare/electron-builder@26.8.0...electron-builder@26.8.1

electron-builder@26.8.0

What's Changed

New Contributors

Full Changelog: https://github.com/electron-userland/electron-builder/compare/electron-builder@26.7.0...electron-builder@26.8.0

electron-builder@26.7.0

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from electron-builder's changelog.

26.8.1

Patch Changes

4edd695 8940ec6 4edd695 dde4309

  • app-builder-lib@26.8.1
  • builder-util@26.8.1
  • dmg-builder@26.8.1

26.8.0

Minor Changes

Patch Changes

cd7c0d9 c18f0eb 769b608 9ba36f9 1b113b7 1b39a8e

  • app-builder-lib@26.8.0
  • builder-util@26.8.0
  • dmg-builder@26.8.0

26.7.0

Patch Changes

bfee115 3fa2d89 ec9e2db aec9157 64b40fe

... (truncated)

Commits
  • 9418d2c chore(deploy): Release v26.8.1 (#9585)
  • 3a3f439 chore(deploy): Release v26.8.0 (electron-updater@6.8.3) (#9556)
  • 1b39a8e feat: adding additional toolsets support for win-codesign/windows-kits (#9430)
  • f1c2ec3 chore(deploy): Release v26.7.0 (electron-updater@6.8.2) (#9549)
  • e394e0c chore(deploy): Release v26.6.0 (#9531)
  • 7b5901b chore(deploy): Release v26.5.0 (electron-updater@6.8.1) (#9503)
  • 06de969 chore(deploy): Release v26.4.1 (electron-updater@6.8.0) (#9458)
  • caf2cb2 chore(deploy): Release v26.4.0 (#9447)
  • 85437a7 chore(deploy): Release v26.3.6 (#9433)
  • 5f9c143 chore(deploy): Release v26.3.5 (electron-updater@6.7.3) (#9422)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for electron-builder since your current version.


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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
build(deps): bump @tootallnate/once and electron-builder
6a53561 
Removes [@tootallnate/once](https://github.com/TooTallNate/once). It's no longer used after updating ancestor dependency [electron-builder](https://github.com/electron-userland/electron-builder/tree/HEAD/packages/electron-builder). These dependencies need to be updated together.


Removes `@tootallnate/once`

Updates `electron-builder` from 25.1.8 to 26.8.1
- [Release notes](https://github.com/electron-userland/electron-builder/releases)
- [Changelog](https://github.com/electron-userland/electron-builder/blob/master/packages/electron-builder/CHANGELOG.md)
- [Commits](https://github.com/electron-userland/electron-builder/commits/electron-builder@26.8.1/packages/electron-builder)

---
updated-dependencies:
- dependency-name: "@tootallnate/once"
  dependency-version: 
  dependency-type: indirect
- dependency-name: electron-builder
  dependency-version: 26.8.1
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 5, 2026
@socket-security
Copy link

socket-security bot commented Mar 5, 2026

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

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedelectron-builder@​25.1.8 ⏵ 26.8.199 +110069 +198 +1100

View full report

@socket-security
Copy link

socket-security bot commented Mar 5, 2026

Caution

Review the following alerts detected in dependencies.

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

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Install-time scripts: npm electron-winstaller during install

Install script: install

Source: node ./script/select-7z-arch.js

From: package-lock.json → npm/electron-builder@26.8.1 → npm/electron-winstaller@5.4.0

ℹ 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 npm/electron-winstaller@5.4.0. 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 Low
Potential code anomaly (AI signal): npm cacache is 100.0% likely to have a medium risk anomaly

Notes: The analyzed code is a straightforward content-cache retrieval and streaming utility. It reads from a cache using an index, supports digest-based access, and optionally memoizes results. There is no evidence of malicious behavior, data exfiltration, backdoors, or external network activity within this module. The security risk appears low, assuming the surrounding system properly manages cache integrity and does not expose untrusted cache contents without validation.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/cacache@19.0.1

ℹ 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 support@socket.dev.

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/cacache@19.0.1. 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 Low
Potential code anomaly (AI signal): npm jiti is 100.0% likely to have a medium risk anomaly

Notes: The fragment implements a sophisticated on-the-fly loader using JITI for transpilation and execution, with careful handling of JSON interop based on nearby package.json type. There is no explicit malicious behavior identified (no external network activity, no hardcoded secrets). However, the dynamic code execution path introduced by _wrapSource and the synthetic module environment represents a potential risk vector if untrusted inputs are loaded, or if jiti/mjs execution context could be manipulated. This warrants strict review of the loader environment, the version and security of JITI, and checks on the sources being loaded to mitigate potential code execution or supply chain concerns.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/jiti@2.6.1

ℹ 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 support@socket.dev.

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/jiti@2.6.1. 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 Low
Potential code anomaly (AI signal): npm minipass-fetch is 100.0% likely to have a medium risk anomaly

Notes: No evidence of malicious behavior or supply-chain sabotage within this code fragment. The code adheres to standard fetch-like behavior with conventional TLS/config handling. Potential security considerations include the ability to disable TLS verification via an environment variable (a known risk if misused) but this is typical for Node.js TLS configurations and not a deliberate backdoor. Overall risk is moderate due to TLS verification control but not due to malicious intent in this module.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/minipass-fetch@4.0.1

ℹ 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 support@socket.dev.

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/minipass-fetch@4.0.1. 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 Low
Potential code anomaly (AI signal): npm mkdirp is 100.0% likely to have a medium risk anomaly

Notes: The code represents a conventional, non-malicious mkdir -p implementation with both asynchronous and synchronous interfaces. Primary security considerations are the default 0777 permissions which may be inappropriate in sensitive directories if not overridden, and potential path traversal risks depending on usage context. No evidence of malware, data leakage, backdoors, or obfuscated malicious behavior was found in this fragment.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/mkdirp@0.5.6

ℹ 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 support@socket.dev.

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/mkdirp@0.5.6. 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 Low
Potential code anomaly (AI signal): npm node-gyp is 100.0% likely to have a medium risk anomaly

Notes: The code is a legitimate Windows registry query and filesystem readability utility, with no inherent malware or backdoors. Primary security concerns are data exposure through verbose logging and the potential misuse of reg.exe with untrusted inputs. Mitigations include restricting input sources, redacting sensitive outputs in logs, and ensuring callers handle registry data securely. Overall security risk is moderate due to sensitive operations and logging exposure, but no active malicious behavior detected.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/node-gyp@11.5.0

ℹ 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 support@socket.dev.

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/node-gyp@11.5.0. 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 Low
Potential code anomaly (AI signal): npm postject is 100.0% likely to have a medium risk anomaly

Notes: While the code contains standard practices for handling file operations and ensures checks for overwriting resources, its primary purpose of injecting resources into executable files carries significant risks for malicious use, particularly in scenarios where the code may be misused for harmful modifications.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/postject@1.0.0-alpha.6

ℹ 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 support@socket.dev.

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/postject@1.0.0-alpha.6. 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 Low
Potential code anomaly (AI signal): npm tar is 100.0% likely to have a medium risk anomaly

Notes: This module acts as a standard tar extraction wrapper using synchronous and asynchronous code paths. There is no evident malicious activity within this fragment. Security risk hinges on the behavior of the Unpack/UnpackSync implementation and how tar entries are written to disk (e.g., path traversal). No hardcoded secrets or network calls are present here. Recommend ensuring tar extraction handles path traversal and destination path sanitization in Unpack, and consider validating opt.file presence and type before streaming.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/electron-builder@26.8.1 → npm/tar@7.5.10

ℹ 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 support@socket.dev.

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/tar@7.5.10. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants