Bump minimatch in /static/node

[dependabot]

Bumps and minimatch. These dependencies needed to be updated together.
Updates minimatch from 3.1.2 to 3.1.5

Commits

• 7bba978 3.1.5
• bd25942 docs: add warning about ReDoS
• 1a9c27c fix partial matching of globstar patterns
• 1a2e084 3.1.4
• ae24656 update lockfile
• b100374 limit recursion for **, improve perf considerably
• 26ffeaa lockfile update
• 9eca892 lock node version to 14
• 00c323b 3.1.3
• 30486b2 update CI matrix and actions
• Additional commits viewable in compare view

Updates minimatch from 3.0.4 to 3.0.4

Commits

• 7bba978 3.1.5
• bd25942 docs: add warning about ReDoS
• 1a9c27c fix partial matching of globstar patterns
• 1a2e084 3.1.4
• ae24656 update lockfile
• b100374 limit recursion for **, improve perf considerably
• 26ffeaa lockfile update
• 9eca892 lock node version to 14
• 00c323b 3.1.3
• 30486b2 update CI matrix and actions
• 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 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.

[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		Network access: npm @truffle/dashboard-message-bus-client in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: static/node/package-lock.json → npm/@truffle/dashboard-message-bus-client@0.1.12 ℹ 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/@truffle/dashboard-message-bus-client@0.1.12. 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		Embedded URLs or IPs: npm @ethersproject/networks URLs: https://www.ethercluster.com/mordor, www.ethercluster.com/etc, www.ethercluster.com/kotti Location: Package overview From: static/node/package-lock.json → npm/@truffle/config@1.2.17 → npm/@truffle/decoder@3.0.16 → npm/@ethersproject/networks@5.8.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/@ethersproject/networks@5.8.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		Embedded URLs or IPs: npm @ethersproject/providers URLs: mainnet.infura.io, goerli.infura.io, sepolia.infura.io, polygon-mainnet.infura.io, polygon-mumbai.infura.io, optimism-mainnet.infura.io, optimism-goerli.infura.io, optimism-sepolia.infura.io, arbitrum-mainnet.infura.io, arbitrum-goerli.infura.io, arbitrum-sepolia.infura.io, https://ethereum.api.nodesmith.io/v1/mainnet/jsonrpc, https://ethereum.api.nodesmith.io/v1/ropsten/jsonrpc, https://ethereum.api.nodesmith.io/v1/rinkeby/jsonrpc, https://ethereum.api.nodesmith.io/v1/goerli/jsonrpc, https://ethereum.api.nodesmith.io/v1/kovan/jsonrpc, ethers.quiknode.pro, ethers.ethereum-goerli.quiknode.pro, ethers.ethereum-sepolia.quiknode.pro, ethers.ethereum-holesky.quiknode.pro, ethers.arbitrum-mainnet.quiknode.pro, ethers.arbitrum-goerli.quiknode.pro, ethers.arbitrum-sepolia.quiknode.pro, ethers.base-mainnet.quiknode.pro, ethers.base-goerli.quiknode.pro, ethers.base-sepolia.quiknode.pro, ethers.bsc.quiknode.pro, ethers.bsc-testnet.quiknode.pro, ethers.matic.quiknode.pro, ethers.matic-testnet.quiknode.pro, ethers.optimism.quiknode.pro, ethers.optimism-goerli.quiknode.pro, ethers.optimism-sepolia.quiknode.pro, ethers.xdai.quiknode.pro, https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sign, tx.to, api.etherscan.io, api-goerli.etherscan.io, api-sepolia.etherscan.io, api.polygonscan.com, api-testnet.polygonscan.com, api.arbiscan.io, api-goerli.arbiscan.io, api-optimistic.etherscan.io, api-goerli-optimistic.etherscan.io, docs.ethers.io/api-keys/, eth-goerli.gateway.pokt.network, eth-mainnet.gateway.pokt.network, poa-kovan.gateway.pokt.network, poly-mainnet.gateway.pokt.network, polygon-mumbai-rpc.gateway.pokt.network, eth-rinkeby.gateway.pokt.network, eth-ropsten.gateway.pokt.network, https://cloudflare-eth.com/, rpc.ankr.com/eth/, rpc.ankr.com/eth_ropsten/, rpc.ankr.com/eth_rinkeby/, rpc.ankr.com/eth_goerli/, rpc.ankr.com/eth_sepolia/, rpc.ankr.com/polygon/, rpc.ankr.com/polygon_mumbai/, rpc.ankr.com/optimism/, rpc.ankr.com/optimism_testnet/, rpc.ankr.com/optimism_sepolia/, rpc.ankr.com/arbitrum/, eth-mainnet.alchemyapi.io/v2/, eth-goerli.g.alchemy.com/v2/, eth-sepolia.g.alchemy.com/v2/, polygon-mainnet.g.alchemy.com/v2/, polygon-mumbai.g.alchemy.com/v2/, arb-mainnet.g.alchemy.com/v2/, arb-goerli.g.alchemy.com/v2/, arb-sepolia.g.alchemy.com/v2/, opt-mainnet.g.alchemy.com/v2/, opt-goerli.g.alchemy.com/v2/, opt-sepolia.g.alchemy.com/v2/, https://gateway.ipfs.io/ipfs/ Location: Package overview From: static/node/package-lock.json → npm/@ethersproject/providers@5.8.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/@ethersproject/providers@5.8.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		Embedded URLs or IPs: npm @truffle/codec URLs: https://github.com/microsoft/TypeScript/issues/18758, https://nodejs.org/api/util.html#util_util_inspect_object_options, https://www.4byte.directory/ Location: Package overview From: static/node/package-lock.json → npm/@truffle/codec@0.17.3 ℹ 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/@truffle/codec@0.17.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		Embedded URLs or IPs: npm @truffle/config URLs: TruffleConfig.search, 0.0.0.0 Location: Package overview From: static/node/package-lock.json → npm/@truffle/config@1.3.61 ℹ 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/@truffle/config@1.3.61. 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		Embedded URLs or IPs: npm @truffle/db URLs: https://graphql.org/, https://pouchdb.com/, https://www.apollographql.com/docs/apollo-server/, https://nodejs.org/api/http.html#http_class_http_server, https://github.com/graphql/graphql-playground, ancestor.id, descendant.id, compilation.id, contract.id, project.id, key.name, sources.0.id, network.name Location: Package overview From: static/node/package-lock.json → npm/@truffle/db@2.0.36 ℹ 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/@truffle/db@2.0.36. 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		Embedded URLs or IPs: npm @truffle/debugger URLs: ImmutableTest.Color.Blue, ReturnValues.fail, InternalsTest.run, ElementaryTest.Ternary.Blue Location: Package overview From: static/node/package-lock.json → npm/@truffle/debugger@12.1.5 ℹ 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/@truffle/debugger@12.1.5. 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		Publisher changed: npm @truffle/promise-tracker is now published by haltman instead of eggplantzzz New Author: haltman Previous Author: eggplantzzz From: static/node/package-lock.json → npm/@truffle/promise-tracker@0.1.7 ℹ 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/@truffle/promise-tracker@0.1.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.
Warn		Embedded URLs or IPs: npm @types/express-serve-static-core URLs: tobi.ferrets.example.com, http://api.example.com/users?page=2, http://api.example.com/users?page=5, http://example.com, https://github.com/visionmedia/consolidate.js Location: Package overview From: static/node/package-lock.json → npm/@types/express-serve-static-core@4.19.8 ℹ 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/@types/express-serve-static-core@4.19.8. 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		Embedded URLs or IPs: npm ajv URLs: http://json-schema.org/draft-07/schema, http://json-schema.org/schema, https://json-schema.org/draft/2020-12/schema, https://json-schema.org/draft/2019-09/schema, https://raw.githubusercontent.com/ajv-validator/ajv/master/lib/refs/data.json# Location: Package overview From: static/node/package-lock.json → npm/ajv@8.18.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/ajv@8.18.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		Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly Notes: The code implements a standard AJV-like dynamic parser generator for JTD schemas. There are no explicit malware indicators in this fragment. The primary security concern is the dynamic code generation and execution from external schemas, which introduces a medium risk if schemas are untrusted. With trusted schemas and proper schema management, the risk is typically acceptable within this pattern. Confidence: 1.00 Severity: 0.60 From: static/node/package-lock.json → npm/ajv@8.18.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/ajv@8.18.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		Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly Notes: The code implements standard timestamp validation with clear logic for normal and leap years and leap seconds. There is no network, file, or execution of external code within this isolated fragment. The only anomalous aspect is assigning a string to validTimestamp.code, which could enable external tooling to inject behavior in certain environments, but this does not constitute active malicious behavior in this isolated snippet. Overall, low to moderate security risk in typical usage; no malware detected within the shown code. Confidence: 1.00 Severity: 0.60 From: static/node/package-lock.json → npm/ajv@8.18.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/ajv@8.18.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		Potential code anomaly (AI signal): npm ajv is 100.0% likely to have a medium risk anomaly Notes: This module generates JavaScript code at runtime via standaloneCode(...) and then immediately executes it with require-from-string. Because the generated code can incorporate user-supplied schemas or custom keywords without sanitization or sandboxing, an attacker who controls those inputs could inject arbitrary code and achieve remote code execution in the Node process. Users should audit and lock down the standaloneCode output or replace dynamic evaluation with a safer, static bundling approach. Confidence: 1.00 Severity: 0.60 From: static/node/package-lock.json → npm/ajv@8.18.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/ajv@8.18.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		Embedded URLs or IPs: npm apollo-server-core URLs: https://github.com/apollographql/apollo-server/issues/4588, https://studio.apollographql.com/graph/, https://schema-reporting.api.apollographql.com/api/graphql, https://go.apollo.dev/s/cache-backends, https://embeddable-explorer.cdn.apollographql.com/, https://embeddable-sandbox.cdn.apollographql.com/, https://apollo-server-landing-page.cdn.apollographql.com/, https://fonts.gstatic.com, https://fonts.googleapis.com/css2?family=Source+Sans+Pro&display=swap, https://github.com/node-fetch/node-fetch/blob/9b9d45881e5ca68757077726b3c0ecf8fdca1f29/src/headers.js#L18, https://github.com/apollographql/apollo-server/pull/3623,, https://github.com/microsoft/TypeScript/issues/9998, https://github.com/DefinitelyTyped/DefinitelyTyped/blob/659eb50d3/types/graphql/utilities/introspectionQuery.d.ts#L31-L37, https://fetch.spec.whatwg.org/#cors-safelisted-request-header, https://github.com/graphql/graphql-spec/pull/384, https://github.com/graphql/graphql-js/issues/3169 Location: Package overview From: static/node/package-lock.json → npm/apollo-server-core@3.13.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/apollo-server-core@3.13.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		Embedded URLs or IPs: npm axios URLs: http://www.google.com, https://nodejs.org/api/http.html#http_message_headers, https://www.npmjs.com/package/form-data, http://url.spec.whatwg.org/#urlutils Location: Package overview From: static/node/package-lock.json → npm/axios@1.5.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/axios@1.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		Publisher changed: npm crypto-addr-codec is now published by leeondamiky instead of makoto_inoue New Author: leeondamiky Previous Author: makoto_inoue From: static/node/package-lock.json → npm/crypto-addr-codec@0.1.8 ℹ 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/crypto-addr-codec@0.1.8. 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		Embedded URLs or IPs: npm ethers URLs: https://links.ethers.org/v5-errors-, https://gateway.ipfs.io/ipfs/, this.network?this.network.name:, network.name:, this.red?, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol#Browser_compatibility, https://github.com/indutny/bn.js/issues/211, links.ethers.org/v5-errors-, https://github.com/adraffy/ens-normalize.js, https://github.com/behnammodi/polyfill/blob/master/array.polyfill.js, https://eips.ethereum.org/EIPS/eip-1559, https://github.com/google/closure-library/blob/8598d87242af59aac233270742c8984e2b2bdbe0/closure/goog/crypt/crypt.js#L117-L143, https://github.com/google/closure-library/blob/master/LICENSE, https://git.io/vad3K, https://github.com/cryptocoinjs/bs58, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis, http://ixti.net/development/javascript/2011/11/11/base64-encodedecode-of-utf8-in-browser-with-js.html, https://tools.ietf.org/html/rfc2315, http://www.requirejs.org/docs/api.html, https://github.com/amdjs/amdjs-api/wiki/AMD, https://www.ietf.org/rfc/rfc4122.txt, https://github.com/ethereum/pyethsaletool, https://github.com/dchest/scrypt-async-js, https://www.npmjs.com/package/scryptsy, https://github.com/ethereum/wiki/wiki/Web3-Secret-Storage-Definition, https://www.ethercluster.com/mordor, https://chainlist.org, https://github.com/satoshilabs/slips/blob/master/slip-0044.md, https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#witness-program, https://datatracker.ietf.org/doc/html/rfc4648#section-5, https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sign, https://geth.ethereum.org/docs/rpc/pubsub, https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#Status_codes, https://dashboard.alchemyapi.io, https://cloudflare-eth.com/ Location: Package overview From: static/node/package-lock.json → npm/ethers@5.8.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/ethers@5.8.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		Embedded URLs or IPs: npm fast-uri URLs: example.com, http://example.com/, http://example.com/foo, http://example.com/foo/, example.com:123/one/two.three?q1=a1&q2=a2#body, example.com:123, 10.10.10.10, 10.10.000.10, 01.01.01.01, 129.144.52.38, uri://10.10.10.10.example.com/en/process, 10.10.10.10.example.com, https://example.com/foo#bar, www.g.com/, www.g.com/adf%0Agf, www.g.com/error%0A/, https://datatracker.ietf.org/doc/html/rfc5954#section-4.1, mple.com, gary.court@gmail.com, example.com:1/path?query#fragment, uri://example.com:9000, uri://www.example.org/red%09ros, uri://www.example.org/red%09ros%C3%A9#red, 192.068.001.000, 192.68.1.0, http://example.org/~user, http://example.org/%7euser, xE9.example.org, uri://xn--rsum-bpad.example.org, uri://www.example.org/D%C3%BCrst, uri://www.example.org/D, uri://www.example.org/D%FCrst, uri://xn--99zt52a.example.org/%e2%80%ae, uri://xn--99zt52a.example.org/%E2%80%AE, http://abc.com:80/~smith/home.html, http://abc.com/~smith/home.html, http://ABC.com/%7Esmith/home.html, http://ABC.com:/%7esmith/home.html, HTTP://ABC.COM, http://abc.com/, http://example.com:/, http://example.com:80/, https://example.com, https://example.com:443/, https://example.com:/, example.com?subject=current-issue, example.com?body=send%20current-issue, example.com?body=send%20current-issue%0D%0Asend%20index, example.org?In-Reply-To=%3C3469A91.D10AF4C@example.com%3E, example.org, example.com?body=subscribe%20bamboo-l, example.com?cc=bob@example.com&body=hello, example.com?cc=bob@example.com?body=hello, example.com?blat=foop, example.org?subject=caf%C3%A9, example.org?subject=%3D%3Futf-8%3FQ%3Fcaf%3DC3%3DA9%3F%3D, example.org?subject=%3D%3Fiso-8859-1%3FQ%3Fcaf%3DE9%3F%3D, example.org?subject=caf%C3%A9&body=caf%C3%A9, 86.example.org?subject=Test&body=NATTO, xn--99zt52a.example.org, example.com?body=current-issue, abc.com, WS://ABC.COM:80/chat#one, ws://abc.com/chat, WSS://ABC.COM:443/chat#one, wss://abc.com/chat, ws://example.com, ws://example.com/foo, ws://example.com/foo?bar, wss://example.com, wss://example.com/foo?bar, wss://example.com/foo, https://datatracker.ietf.org/doc/html/rfc3986#section-5.2.4 Location: Package overview From: static/node/package-lock.json → npm/fast-uri@3.1.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/fast-uri@3.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		Embedded URLs or IPs: npm uuid URLs: http://www.movable-type.co.uk/scripts/sha1.html, https://github.com/uuidjs/uuid#getrandomvalues-not-supported Location: Package overview From: static/node/package-lock.json → npm/uuid@9.0.1 ℹ 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/uuid@9.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		Embedded URLs or IPs: npm ws URLs: https://www.cl.cam.ac.uk/%7Emgk25/ucs/utf8_check.c, https://html.spec.whatwg.org/multipage/comms.html#the-websocket-interface, https://github.com/websockets/ws/issues/1869., https://github.com/websockets/ws/issues/1940. Location: Package overview From: static/node/package-lock.json → npm/ws@8.18.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/ws@8.18.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		Environment variable access: npm ws reads WS_NO_BUFFER_UTIL Env Vars: WS_NO_BUFFER_UTIL Location: Package overview From: static/node/package-lock.json → npm/ws@8.18.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/ws@8.18.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		Potential code anomaly (AI signal): npm ws is 100.0% likely to have a medium risk anomaly Notes: The code implements a standard EventTarget-like mixin for wrapping event listeners and dispatching events to user callbacks. There are no suspicious patterns such as dynamic code execution, hardcoded secrets, or network activity. The risk is contingent on what the consumer does inside their handlers; the snippet itself does not introduce malware or data leakage mechanisms beyond normal event dispatch. Overall security risk is low in isolation. Confidence: 1.00 Severity: 0.60 From: static/node/package-lock.json → npm/ws@8.18.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/ws@8.18.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		Environment variable access: npm ws reads WS_NO_UTF_8_VALIDATE Env Vars: WS_NO_UTF_8_VALIDATE Location: Package overview From: static/node/package-lock.json → npm/ws@8.18.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/ws@8.18.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.

View full report