Module: globalThis["fetch"]

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.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/@actions/github@9.0.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.

Did you mean: json-~~with-~~bigint**-string**

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/json-with-bigint@3.5.7

ℹ Read more on: This package | This alert | What is AI-detected potential typosquatting?

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: Given the AI system's identification of this package as a potential typosquat, please verify that you did not intend to install a different package. Be cautious, as malicious packages often use names similar to popular ones.

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

Module: globalThis["fetch"]

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

URLs: https://api.github.com, https://github.com, https://api.github.com/graphql

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

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

URLs: https://docs.github.com/rest/orgs/security-managers#add-a-security-manager-team, https://docs.github.com/rest/orgs/security-managers#list-security-manager-teams, https://docs.github.com/rest/orgs/security-managers#remove-a-security-manager-team, https://uploads.github.com, https://docs.github.com/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks, https://docs.github.com/rest/guides/encrypting-secrets-for-the-rest-api, https://pynacl.readthedocs.io/en/latest/public/#nacl-public-sealedbox, https://www.nuget.org/packages/Sodium.Core/, https://github.com/RubyCrypto/rbnacl, https://libsodium.gitbook.io/doc/bindings_for_other_languages, https://github.com/octo-org, https://docs.github.com/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization, https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository, https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-a-private-repository, https://github.blog/changelog/2025-02-02-actions-get-workflow-usage-and-get-workflow-run-usage-endpoints-closing-down/, https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions, https://docs.github.com/actions/deployment/targeting-different-environments/using-environments-for-deployment, https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia, https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types, https://docs.github.com/rest/activity/notifications#list-notifications-for-the-authenticated-user, https://docs.github.com/rest/activity/notifications#list-repository-notifications-for-the-authenticated-user, https://github.com/notifications., https://docs.github.com/rest/guides/getting-started-with-the-rest-api#http-method, https://docs.github.com/apps/building-github-apps/creating-github-apps-from-a-manifest/, https://github.com/settings/applications#authorized, https://docs.github.com/rest/apps/apps#suspend-an-app-installation, https://docs.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app, https://docs.github.com/rest/apps/apps#list-installations-for-the-authenticated-app, https://github.com/settings/apps/:app_slug, https://docs.github.com/rest/authentication/authenticating-to-the-rest-api#using-basic-authentication, https://docs.github.com/rest/apps/apps#create-an-installation-access-token-for-an-app, https://docs.github.com/billing/using-the-new-billing-platform, https://docs.github.com/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages, https://docs.github.com/rest/checks/runs, https://docs.github.com/rest/checks/suites#update-repository-preferences-for-check-suites, https://docs.github.com/rest/actions/workflow-runs#re-run-a-job-from-a-workflow-run, https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html, https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization, https://docs.github.com/code-security/code-scanning/troubleshooting-sarif, https://docs.github.com/code-security/code-scanning/troubleshooting-sarif/results-exceed-limit, https://docs.github.com/rest/codespaces/organization-secrets#create-or-update-an-organization-secret, https://docs.github.com/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-the-copilot-subscription-for-your-organization/about-billing-for-github-copilot-in-your-organization, https://docs.github.com/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-the-copilot-subscription-for-your-organization/subscribing-to-copilot-for-your-organization, https://docs.github.com/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization#policies-for-suggestion-matching, https://docs.github.com/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/revoking-access-to-copilot-for-members-of-your-organization, https://docs.github.com/copilot/managing-copilot/managing-policies-for-copilot-business-in-your-organization, https://docs.github.com/copilot/reference/metrics-data, https://docs.github.com/rest/dependabot/secrets#create-or-update-an-organization-secret, https://github.com/github/tweetsodium, https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts, https://docs.github.com/rest/guides/using-pagination-in-the-rest-api, https://git-scm.com/book/en/v2/Git-Internals-Git-Objects, https://docs.github.com/rest/git/refs#create-a-reference, https://docs.github.com/rest/git/commits#create-a-commit, https://docs.github.com/rest/git/refs#update-a-reference, https://docs.github.com/rest/guides/getting-started-with-the-git-database-api#checking-mergeability-of-pull-requests, https://docs.github.com/rest/pulls/pulls#get-a-pull-request, https://git-scm.com/book/en/v2/Git-Internals-Git-References, https://docs.github.com/rest/using-the-rest-api/rate-limits-for-the-rest-api#about-secondary-rate-limits, https://docs.github.com/rest/guides/best-practices-for-using-the-rest-api, https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications, https://docs.github.com/rest/pulls/pulls#list-pull-requests, https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository, https://docs.github.com/articles/about-github-s-ip-addresses/, https://docs.github.com/rest/migrations/users#start-a-user-migration, https://docs.github.com/rest/repos/repos#delete-a-repository, https://docs.github.com/rest/orgs/organization-roles, https://docs.github.com/organizations/managing-peoples-access-to-your-organization-with-roles/using-organization-roles, https://docs.github.com/articles/converting-an-organization-member-to-an-outside-collaborator/, https://docs.github.com/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories, https://docs.github.com/site-policy/github-terms/github-terms-of-service, https://docs.github.com/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization, https://docs.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/, https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers, https://cli.github.com/manual/gh_attestation_verify, https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds, https://docs.github.com/articles/publicizing-or-concealing-organization-membership, https://docs.github.com/rest/orgs/orgs#list-organizations-for-the-authenticated-user, https://docs.github.com/webhooks/#ping-event, https://docs.github.com/rest/orgs/members#get-organization-membership-for-a-user, https://developer.github.com/changes/2019-12-03-internal-visibility-changes, https://docs.github.com/rest/code-security/configurations#set-a-code-security-configuration-as-a-default-for-an-organization, https://github.blog/changelog/2024-07-09-sunsetting-security-settings-defaults-parameters-in-the-organizations-rest-api/, https://docs.github.com/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages, https://docs.github.com/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages, https://docs.github.com/github/getting-started-with-github/githubs-products, https://docs.github.com/rest/pulls/reviews#submit-a-review-for-a-pull-request, https://docs.github.com/rest/branches/branch-protection, https://docs.github.com/rest/pulls/pulls/#create-a-pull-request, https://docs.github.com/rest/pulls/pulls#update-a-pull-request, https://docs.github.com/articles/about-merge-methods-on-github/, https://docs.github.com/articles/about-merge-methods-on-github/#squashing-your-merge-commits, https://docs.github.com/articles/about-merge-methods-on-github/#rebasing-and-merging-your-commits, https://git-scm.com/docs/git-diff, https://support.github.com/, https://docs.github.com/rest/commits/commits#list-commits, https://docs.github.com/rest/pulls/reviews#list-reviews-for-a-pull-request, https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits, https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits, https://docs.github.com/rest/pulls/reviews#create-a-review-for-a-pull-request, https://docs.github.com/rest/search/search, https://docs.github.com/rest/search/search#search-code, https://docs.github.com/graphql/overview/resource-limitations#rate-limit, https://docs.github.com/apps/creating-github-apps/setting-up-a-github-app/creating-a-github-app-from-a-manifest#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration, https://docs.github.com/rest/dependency-graph, https://docs.github.com/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github, https://docs.github.com/rest/actions/self-hosted-runners, https://docs.github.com/rest/about-the-rest-api/api-versions, https://docs.github.com/rest/commits/comments#get-a-commit-comment, https://docs.github.com/rest/issues/issues#get-an-issue, https://docs.github.com/rest/issues/comments#get-an-issue-comment, https://docs.github.com/rest/pulls/comments#get-a-review-comment-for-a-pull-request, https://docs.github.com/rest/releases/releases#get-a-release, https://docs.github.com/rest/teams/discussion-comments#get-a-discussion-comment, https://docs.github.com/rest/teams/discussions#get-a-discussion, https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization, https://docs.github.com/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators, https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization, https://docs.github.com/rest/collaborators/invitations, https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests, https://docs.github.com/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories, https://github.com/actions/attest, https://docs.github.com/rest/commits/statuses, https://docs.github.com/rest/apps/apps#get-an-app, https://docs.github.com/actions/managing-workflow-runs-and-deployments/managing-deployments/creating-custom-deployment-protection-rules, https://docs.github.com/webhooks/event-payloads/#repository_dispatch, https://support.github.com/contact?tags=dotcom-rest-api, https://docs.github.com/rest/repos/contents/#delete-a-file, https://docs.github.com/rest/repos/repos#get-a-repository, https://docs.github.com/articles/configuring-automated-security-fixes, https://docs.github.com/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability, https://docs.github.com/articles/about-security-alerts-for-vulnerable-dependencies, https://docs.github.com/articles/signing-commits-with-gpg, https://docs.github.com/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories, https://github.com/github/markup, https://git.io/v1YCW, https://docs.github.com/rest/git/trees#get-a-tree, https://docs.github.com/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization#viewing-insights-for-rulesets, https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#viewing-insights-for-rulesets, https://docs.github.com/repositories/viewing-activity-and-data-for-your-repository, https://docs.github.com/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks, https://docs.github.com/github/administering-a-repository/renaming-a-branch, https://docs.github.com/articles/about-repository-transfers/, https://docs.github.com/rest/releases/releases#create-a-release, http://en.wikipedia.org/wiki/Server_Name_Indication, https://www.iana.org/assignments/media-types/media-types.xhtml, https://docs.github.com/rest/releases/releases#get-the-latest-release, https://docs.github.com/rest/search/search#text-match-metadata, https://github.com/jquery/jquery, https://github.com/search?utf8=%E2%9C%93&q=language%3Ago&type=Code, https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ago&type=Code, https://github.com/octocat/Spoon-Knife, https://github.com/topics., https://docs.github.com/get-started/learning-about-github/about-github-advanced-security, https://docs.github.com/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory#requesting-a-cve-identification-number-optional, https://docs.github.com/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database#about-types-of-security-advisories, https://docs.github.com/articles/synchronizing-teams-between-your-identity-provider-and-github/, https://docs.github.com/articles/setting-team-creation-permissions-in-your-organization, https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/about-teams, https://docs.github.com/rest/teams/teams#create-a-team, https://docs.github.com/enterprise-cloud@latest/admin/managing-iam/understanding-iam-for-enterprises/about-enterprise-managed-users, https://github.com/settings/profile, https://docs.github.com/rest/guides/getting-started-with-the-rest-api#authentication, https://docs.github.com/rest/users/emails

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/@octokit/plugin-rest-endpoint-methods@17.0.0

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@octokit/plugin-rest-endpoint-methods@17.0.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.

URLs: https://raw.githubusercontent.com/Ivan-Korolenko/json-with-bigint.performance.json/refs/heads/main/performance.json

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/json-with-bigint@3.5.7

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

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

URLs: https://github.com/node-fetch/fetch-blob/blob/8ab587d34080de94140b54f07168451e7d0b655e/index.js#L229-L241, https://developer.mozilla.org/en-US/docs/Web/API/URL/URL:, https://github.com/nodejs/node/pull/38505/files, https://github.com/nodejs/node/pull/46528, https://github.com/nodejs/undici/pull/319, https://tools.ietf.org/html/rfc7230#section-3.2.6, https://github.com/nodejs/node/blob/main/lib/_http_common.js, https://www.rfc-editor.org/rfc/rfc9110#field.content-range, https://github.com/nodejs/undici/issues/2630, https://github.com/curl/curl/blob/3434c6b46e682452973972e8313613dfa58cd690/lib/mime.c#L1029-L1030, https://github.com/form-data/form-data/issues/63, https://fetch.spec.whatwg.org/#bodyinit-safely-extract, https://fetch.spec.whatwg.org/#concept-body-clone, https://fetch.spec.whatwg.org/#concept-body-consume-body, https://fetch.spec.whatwg.org/#body-unusable, https://infra.spec.whatwg.org/#parse-json-bytes-to-a-javascript-value, https://fetch.spec.whatwg.org/#concept-body-mime-type, https://tools.ietf.org/html/rfc7230#section-6.3.2, https://mimesniff.spec.whatwg.org/#parse-a-mime-type, https://developer.mozilla.org/en-US/docs/Web/API/Blob, https://developer.mozilla.org/en-US/docs/Web/API/File, https://fetch.spec.whatwg.org/#body-mixin, https://tools.ietf.org/html/rfc7540#section-8.3, https://tools.ietf.org/html/rfc7231#section-4.3.1, https://tools.ietf.org/html/rfc7231#section-4.3.2, https://tools.ietf.org/html/rfc7231#section-4.3.5, https://tools.ietf.org/html/rfc7230#section-3.3.2, https://github.com/nodejs/undici/issues/2046, CacheStorage.open, https://fetch.spec.whatwg.org/#response-create, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry, https://fetch.spec.whatwg.org/#typedefdef-xmlhttprequestbodyinit, https://fetch.spec.whatwg.org/#bodyinit, https://tools.ietf.org/html/rfc2616, https://tools.ietf.org/html/rfc7230, https://github.com/chromium/chromium/blob/94.0.4604.1/third_party/blink/renderer/core/fetch/response.cc#L116, https://fetch.spec.whatwg.org/#header-name, https://fetch.spec.whatwg.org/#header-value, https://w3c.github.io/webappsec-referrer-policy/#set-requests-referrer-policy-on-redirect, https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#specify_a_fallback_policy, https://fetch.spec.whatwg.org/#cross-origin-resource-policy-check, https://fetch.spec.whatwg.org/#concept-cors-check, https://fetch.spec.whatwg.org/#concept-tao-check, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-dest-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-mode-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-site-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-user-header, https://fetch.spec.whatwg.org/#append-a-request-origin-header, https://html.spec.whatwg.org/multipage/origin.html#clone-a-policy-container, https://w3c.github.io/webappsec-referrer-policy/#determine-requests-referrer, https://github.com/web-platform-tests/wpt/commit/e4c5cc7a5e48093220528dfdd1c4012dc3837a0e, https://webidl.spec.whatwg.org/#iterator-result, https://webidl.spec.whatwg.org/#dfn-iterator-prototype-object, https://fetch.spec.whatwg.org/#body-fully-read, https://infra.spec.whatwg.org/#isomorphic-encode, https://streams.spec.whatwg.org/#readablestreamdefaultreader-read-all-bytes, https://streams.spec.whatwg.org/#read-loop, https://fetch.spec.whatwg.org/#is-local, https://fetch.spec.whatwg.org/#simple-range-header-value, https://fetch.spec.whatwg.org/#build-a-content-range, https://fetch.spec.whatwg.org/#concept-header-list-get-decode-split, https://encoding.spec.whatwg.org/#utf-8-decode, https://fetch.spec.whatwg.org/#concept-main-fetch, https://fetch.spec.whatwg.org/#concept-scheme-fetch, https://github.com/nodejs/undici/issues/1776, https://github.com/web-platform-tests/wpt/blob/7b0ebaccc62b566a1965396e5be7bb2bc06f841f/FileAPI/url/resources/fetch-tests.js#L52-L56, https://github.com/nodejs/undici/issues/1193., https://fetch.spec.whatwg.org/#http-redirect-fetch, https://fetch.spec.whatwg.org/#cors-non-wildcard-request-header-name, https://fetch.spec.whatwg.org/#authentication-entries, https://github.com/whatwg/fetch/issues/1293, https://fetch.spec.whatwg.org/#http-network-fetch, https://websockets.spec.whatwg.org/#feedback-from-the-protocol, https://datatracker.ietf.org/doc/html/rfc6455#section-7.1.4

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.0

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

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

Env Vars: NODE_V8_COVERAGE

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: UNDICI_NO_FG

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: JEST_WORKER_ID

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: http_proxy

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: HTTP_PROXY

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: https_proxy

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: HTTPS_PROXY

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: no_proxy

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: NO_PROXY

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Env Vars: CI

Location: Package overview

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.

Notes: The analyzed code appears to implement a standard in-memory cache batch operation flow (put/delete) with careful handling of response bodies by buffering and storing bytes for caching. No signs of malware, data exfiltration, backdoors, or obfuscated behavior were found. The primary security considerations relate to memory usage from buffering potentially large response bodies and ensuring robust validation within batch operations to prevent cache state corruption. Overall risk is moderate, driven by in-memory data handling rather than external communication.

Confidence: 1.00

Severity: 0.60

From: .github/labelChecker/package-lock.json → npm/@actions/github@9.0.0 → npm/undici@6.23.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/undici@6.23.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.