Skip to content

chore: Bump @metamask/auto-changelog from 7.0.1 to 7.1.0 - #4189

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/main/metamask/auto-changelog-7.1.0
Open

dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/main/metamask/auto-changelog-7.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @metamask/auto-changelog from 7.0.1 to 7.1.0.

Commits
  • 5248732 Release 3.0.0 (#143)
  • 99aa4d8 fix(create-release-branch): allow empty "Initialize Release" commit (#142)
  • 7b4141f feat(auto-changelog): add --all flag to validate and update (#132)
  • 49ebb8e chore(dev-deps): bump @lavamoat/allow-scripts from ^3.0.4 to ^5.1.0 (#133)
  • edf4bb7 feat: add changesets-lint CLI (#131)
  • See full diff in compare view

@dependabot
dependabot Bot requested a review from a team as a code owner November 18, 2026 06:05
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 18, 2026
@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:06 Active
@socket-security

socket-security Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​types/​semver@​7.5.0 ⏵ 7.8.01001007481100
Updated@​metamask/​auto-changelog@​7.0.1 ⏵ 7.1.099 +110010097 +1100

View full report

@socket-security

socket-security Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Caution

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Network access: npm @yarnpkg/core in module https

Module: https

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.1

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yarnpkg/core@4.9.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 priority
Network access: npm @yarnpkg/core in module http

Module: http

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.1

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yarnpkg/core@4.9.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 priority
Network access: npm @yarnpkg/core in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.1

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yarnpkg/core@4.9.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 priority
Network access: npm cacheable-lookup in module dns

Module: dns

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/cacheable-lookup@5.0.4

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cacheable-lookup@5.0.4. 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 priority
Network access: npm hpagent in module https

Module: https

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/hpagent@1.2.0

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hpagent@1.2.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 priority
Network access: npm hpagent in module http

Module: http

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/hpagent@1.2.0

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hpagent@1.2.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 priority
Network access: npm http2-wrapper in module tls

Module: tls

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/http2-wrapper@1.0.3

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/http2-wrapper@1.0.3. 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 priority
Network access: npm http2-wrapper in module http2

Module: http2

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/http2-wrapper@1.0.3

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/http2-wrapper@1.0.3. 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 priority
Network access: npm http2-wrapper in module http

Module: http

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/http2-wrapper@1.0.3

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/http2-wrapper@1.0.3. 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 priority
Network access: npm http2-wrapper in module https

Module: https

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/http2-wrapper@1.0.3

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/http2-wrapper@1.0.3. 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 priority
Network access: npm http2-wrapper in module net

Module: net

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/http2-wrapper@1.0.3

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/http2-wrapper@1.0.3. 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 priority
Network access: npm resolve-alpn in module tls

Module: tls

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/resolve-alpn@1.2.1

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/resolve-alpn@1.2.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 priority
Potential code anomaly (AI signal): npm tar is 66.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: 0.66

Severity: 0.56

From: package.json → npm/@lavamoat/allow-scripts@4.0.0 → npm/rollup@2.80.0 → npm/vite@6.4.5 → npm/@metamask/auto-changelog@7.1.0 → npm/crypto-browserify@3.12.1 → npm/@jest/expect@29.5.0 → npm/jest@29.5.0 → npm/webpack-dev-server@5.2.2 → npm/fork-ts-checker-webpack-plugin@9.0.2 → npm/tsx@4.20.3 → npm/ts-jest@29.1.1 → npm/tar@7.5.23

ℹ 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.23. 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 priority
Network access: npm got in module http

Module: http

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/got@11.8.6

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/got@11.8.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 priority
Network access: npm got in module https

Module: https

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/got@11.8.6

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/got@11.8.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 priority
Network access: npm got in module net

Module: net

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/got@11.8.6

ℹ Read more on: This package | This alert | What is network access?

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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/got@11.8.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 priority
Publisher changed: npm clone-response is now published by sindresorhus instead of lukechilds

New Author: sindresorhus

Previous Author: lukechilds

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/clone-response@1.0.3

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/clone-response@1.0.3. 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.

Block
Low priority
Publisher changed: npm responselike is now published by sindresorhus instead of lukechilds

New Author: sindresorhus

Previous Author: lukechilds

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/responselike@2.0.1

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/responselike@2.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.

Block
Low priority
Environment variable access: npm @metamask/auto-changelog

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0

ℹ Read more on: This package | This alert | What is environment variable access?

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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@7.1.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 priority
Environment variable access: npm @metamask/auto-changelog reads npm_package_repository_url

Env Vars: npm_package_repository_url

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0

ℹ Read more on: This package | This alert | What is environment variable access?

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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@7.1.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 priority
Environment variable access: npm @metamask/auto-changelog reads PROJECT_CWD

Env Vars: PROJECT_CWD

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0

ℹ Read more on: This package | This alert | What is environment variable access?

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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/auto-changelog@7.1.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 priority
Potential code anomaly (AI signal): npm @yarnpkg/core is 66.0% likely to have a medium risk anomaly

Notes: No explicit embedded malware payload is evident in this fragment. However, it implements a high-impact supply-chain mechanism: it can download remote plugin code (HTTP(S)), persist it to disk, and dynamically require/activate it based on rc/environment-controlled configuration. If an attacker can influence configuration inputs (rc files, injected env files, or environment variables), this becomes a straightforward path to arbitrary code execution via plugin initialization. Review should focus on who can modify those inputs and what additional trust controls exist outside this module (e.g., signature verification or strict allowlisting of plugin sources).

Confidence: 0.66

Severity: 0.68

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.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/@yarnpkg/core@4.9.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 priority
Environment variable access: npm @yarnpkg/core

Env Vars: YARN_CACHE_CHECKPOINT_OVERRIDE

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.1

ℹ Read more on: This package | This alert | What is environment variable access?

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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yarnpkg/core@4.9.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 priority
Environment variable access: npm @yarnpkg/core reads YARN_CACHE_VERSION_OVERRIDE

Env Vars: YARN_CACHE_VERSION_OVERRIDE

Location: Package overview

From: package.json → npm/@metamask/auto-changelog@7.1.0 → npm/@yarnpkg/core@4.9.1

ℹ Read more on: This package | This alert | What is environment variable access?

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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yarnpkg/core@4.9.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
See 25 more rows in the dashboard

View full report

@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:07 Active
@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:08 Active
@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:10 Active
@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:10 Active
@dependabot
dependabot Bot deployed to default-branch November 18, 2026 06:13 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:13 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:14 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:15 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:17 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:17 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 18, 2026 06:18 Active
Bumps [@metamask/auto-changelog](https://github.com/MetaMask/release-tools) from 7.0.1 to 7.1.0.
- [Release notes](https://github.com/MetaMask/release-tools/releases)
- [Commits](https://github.com/MetaMask/release-tools/compare/@metamask/auto-changelog@7.0.1...@metamask/auto-changelog@7.1.0)

---
updated-dependencies:
- dependency-name: "@metamask/auto-changelog"
  dependency-version: 7.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/main/metamask/auto-changelog-7.1.0 branch from 76f4f1a to 3ab0b9e Compare November 20, 2026 11:36
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:37 Active
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:38 Active
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:39 Active
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:41 Active
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:41 Active
@dependabot
dependabot Bot deployed to default-branch November 20, 2026 11:43 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:44 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:45 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:46 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:47 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:47 Active
@metamask-ci
metamask-ci Bot deployed to default-branch November 20, 2026 11:49 Active
@codecov

codecov Bot commented Nov 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.69%. Comparing base (52a70c6) to head (2255171).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4189   +/-   ##
=======================================
  Coverage   98.69%   98.69%           
=======================================
  Files         429      429           
  Lines       12541    12541           
  Branches     1987     1987           
=======================================
  Hits        12377    12377           
  Misses        164      164           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

This branch was successfully deployed

1 active deployment
default-branch — 22551715 Deployed Nov 20, 2026 by metamask-ci[bot] via Update pull request / Commit result #10458
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant