chore(deps): bump lodash from 4.17.21 to 4.17.23

[dependabot]

Bumps lodash from 4.17.21 to 4.17.23.

Commits

• dec55b7 Bump main to v4.17.23 (#6088)
• 19c9251 fix: setCacheHas JSDoc return type should be boolean (#6071)
• b5e6729 jsdoc: Add -0 and BigInt zeros to _.compact falsey values list (#6062)
• edadd45 Prevent prototype pollution on baseUnset function
• 4879a7a doc: fix autoLink function, conversion of source links (#6056)
• 9648f69 chore: remove yarn.lock file (#6053)
• dfa407d ci: remove legacy configuration files (#6052)
• 156e196 feat: add renovate setup (#6039)
• 933e106 ci: add pipeline for Bun (#6023)
• 072a807 docs: update links related to Open JS Foundation (#5968)
• 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]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	remark-preset-lint-consistent@​6.0.0
	remark-preset-lint-markdown-style-guide@​6.0.0
	remark-lint-no-shell-dollars@​4.0.0
	remark-preset-lint-recommended@​7.0.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

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

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Embedded URLs or IPs: npm lodash URLs: _.map, _.at, _.gt, _.lt, https://bugs.webkit.org/show_bug.cgi?id=156034, _.rest, _.property, http://ecma-international.org/ecma-262/7.0/#sec-samevaluezero, http://ecma-international.org/ecma-262/7.0/#sec-ecmascript-function-objects-call-thisargument-argumentslist, https://mdn.io/Array/slice, https://en.wikipedia.org/wiki/Empty_set, https://en.wikipedia.org/wiki/Vacuous_truth, https://mdn.io/Structured_clone_algorithm, https://mdn.io/Number/isFinite, http://ecma-international.org/ecma-262/7.0/#sec-tolength, http://www.ecma-international.org/ecma-262/7.0/#sec-ecmascript-language-types, https://mths.be/he, https://mathiasbynens.be/notes/ambiguous-ampersands, http://wonko.com/post/html-escaping, http://requirejs.org/docs/errors.html#mismatch, https://css-tricks.com/debouncing-throttling-explained-examples/, https://lodash.com/, https://npms.io/search?q=ponyfill., http://ecma-international.org/ecma-262/7.0/#sec-patterns, http://ecma-international.org/ecma-262/7.0/#sec-template-literal-lexical-components, https://en.wikipedia.org/wiki/Combining_Diacritical_Marks, https://en.wikipedia.org/wiki/Combining_Diacritical_Marks_for_Symbols, https://mathiasbynens.be/notes/javascript-unicode, http://eev.ee/blog/2015/09/12/dark-corners-of-unicode/, http://ecma-international.org/ecma-262/7.0/#sec-object.prototype.tostring, https://en.wikipedia.org/wiki/Exponentiation_by_squaring, https://mdn.io/clearTimeout, https://github.com/jashkenas/underscore/pull/1247, https://bugs.chromium.org/p/v8/issues/detail?id=90, https://es5.github.io/#x13.2.2, https://mdn.io/round#Examples, http://www.ecma-international.org/ecma-262/7.0/#sec-regexp.prototype.tostring, http://ecma-international.org/ecma-262/7.0/#sec-object.keys, https://bugs.chromium.org/p/v8/issues/detail?id=2070, https://mdn.io/setTimeout, https://mdn.io/Array/reverse, https://mdn.io/iteration_protocols#iterator, https://en.wikipedia.org/wiki/Fisher-Yates_shuffle, http://peter.michaux.ca/articles/lazy-function-definition-pattern, http://ecma-international.org/ecma-262/7.0/#sec-properties-of-the-map-prototype-object, https://mdn.io/rest_parameters, http://www.ecma-international.org/ecma-262/7.0/#sec-function.prototype.apply, https://mdn.io/spread_operator, https://mdn.io/Number/isInteger, https://mdn.io/Number/isNaN, https://mdn.io/isNaN, https://www.npmjs.com/package/babel-polyfill, https://mdn.io/Number/isSafeInteger, http://www.ecma-international.org/ecma-262/7.0/#sec-tointeger, https://mdn.io/Object/assign, https://en.wikipedia.org/wiki/Letter_case#Special_case_styles, https://es5.github.io/#x15.1.2.2, https://mdn.io/String/replace, https://en.wikipedia.org/wiki/Snake_case, https://mdn.io/String/split, https://en.wikipedia.org/wiki/Letter_case#Stylistic_or_specialised_usage, http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/#toc-sourceurl, https://lodash.com/custom-builds, https://developer.chrome.com/extensions/sandboxingEval, https://github.com/olado/doT, https://mdn.io/toLowerCase, https://mdn.io/toUpperCase Location: Package overview From: ? → npm/cypress@14.5.3 → npm/lodash@4.17.23 ℹ 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/lodash@4.17.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		Embedded URLs or IPs: npm remark-lint-no-multiple-toplevel-headings URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-multiple-toplevel-headings#readme Location: Package overview From: ? → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-no-multiple-toplevel-headings@4.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/remark-lint-no-multiple-toplevel-headings@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-shell-dollars URLs: sh.in, https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-shell-dollars#readme Location: Package overview From: .ci/remark-lint/package.json → npm/remark-lint-no-shell-dollars@4.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/remark-lint-no-shell-dollars@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-shortcut-reference-image URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-shortcut-reference-image#readme Location: Package overview From: ? → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-no-shortcut-reference-image@4.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/remark-lint-no-shortcut-reference-image@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-shortcut-reference-link URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-shortcut-reference-link#readme Location: Package overview From: ? → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-no-shortcut-reference-link@4.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/remark-lint-no-shortcut-reference-link@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-table-indentation URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-table-indentation#readme Location: Package overview From: ? → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-no-table-indentation@5.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/remark-lint-no-table-indentation@5.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-undefined-references URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-undefined-references#readme Location: Package overview From: ? → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-lint-no-undefined-references@5.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/remark-lint-no-undefined-references@5.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.
Warn		Embedded URLs or IPs: npm remark-lint-no-unused-definitions URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-no-unused-definitions#readme Location: Package overview From: ? → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-lint-no-unused-definitions@4.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/remark-lint-no-unused-definitions@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-ordered-list-marker-style URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-ordered-list-marker-style#readme Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-ordered-list-marker-style@4.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/remark-lint-ordered-list-marker-style@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-ordered-list-marker-value URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-ordered-list-marker-value#readme Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-ordered-list-marker-value@4.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/remark-lint-ordered-list-marker-value@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-rule-style URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-rule-style#readme Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-rule-style@4.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/remark-lint-rule-style@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-strong-marker URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-strong-marker#readme Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-strong-marker@4.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/remark-lint-strong-marker@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-table-cell-padding URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-table-cell-padding#readme Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-table-cell-padding@5.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/remark-lint-table-cell-padding@5.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.
Warn		Embedded URLs or IPs: npm remark-lint-table-pipe-alignment URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-table-pipe-alignment#readme Location: Package overview From: ? → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-table-pipe-alignment@4.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/remark-lint-table-pipe-alignment@4.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.
Warn		Embedded URLs or IPs: npm remark-lint-table-pipes URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-table-pipes#readme Location: Package overview From: ? → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-table-pipes@5.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/remark-lint-table-pipes@5.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.
Warn		Embedded URLs or IPs: npm remark-lint-unordered-list-marker-style URLs: https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-unordered-list-marker-style#readme Location: Package overview From: ? → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-lint-unordered-list-marker-style@4.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/remark-lint-unordered-list-marker-style@4.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.
Warn		Debug access: npm require-from-string in module module Module: module Location: Package overview From: ? → npm/remark-lint-frontmatter-schema@3.15.4 → npm/require-from-string@2.0.2 ℹ Read more on: This package | This alert | What is debug 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: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/require-from-string@2.0.2. 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 text-table is 100.0% likely to have a medium risk anomaly Notes: The code is a standard, non-malicious text-table formatter module. It operates purely on provided data (rows and options) and returns a formatted string. No evidence of malicious behavior, data exfiltration, or security vulnerabilities inherent to the code path. Potential security risk is minimal and related only to proper usage of external inputs at a higher level; within this module, data handling is limited to string processing and formatting. Confidence: 1.00 Severity: 0.60 From: ? → npm/remark-cli@12.0.1 → npm/text-table@0.2.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/text-table@0.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		Embedded URLs or IPs: npm type-fest URLs: _source.name, https://github.com/microsoft/TypeScript/issues/26223, https://github.com/pajecawav/tiny-global-store/blob/master/src/index.ts, https://codemix.com/opaque-types-in-javascript/, https://github.com/microsoft/TypeScript/issues/202, https://github.com/microsoft/TypeScript/issues/15408, https://github.com/microsoft/TypeScript/issues/15807, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/join#description, https://github.com/microsoft/TypeScript/issues/31438, https://github.com/sindresorhus/pageres/blob/4a5d05fca19a5fbd2f53842cbf3eb7b1b63bddd2/source/index.ts#L72, https://stackoverflow.com/questions/50703834, https://github.com/microsoft/TypeScript/issues/24509, https://webpack.js.org/guides/tree-shaking/, https://classic.yarnpkg.com/blog/2018/02/15/nohoist/, https://github.com/npm/rfcs/issues/287, https://github.com/isaacs/minimatch, https://nodejs.org/api/esm.html#esm_package_json_type_field, https://nodejs.org/api/packages.html#subpath-exports, https://nodejs.org/api/packages.html#subpath-imports, https://github.com/npm/rfcs/blob/latest/implemented/0010-monorepo-subdirectory-declaration.md, https://github.com/npm/rfcs/blob/latest/accepted/0017-add-funding-support.md, https://docs.npmjs.com/cli/using-npm/workspaces, https://classic.yarnpkg.com/docs/workspaces/, https://nodejs.org/api/packages.html#nodejs-packagejson-field-definitions, https://nodejs.org/api/corepack.html#supported-package-managers, https://nodejs.org/api/corepack.html, https://docs.npmjs.com/cli/v7/configuring-npm/package-json#publishconfig, https://registry.npmjs.org/, https://github.com/andnp/SimplyTyped/blob/master/src/types/strings.ts, https://github.com/yankeeinlondon/native-dash/blob/master/src/capitalize.ts, https://github.com/inocan-group/inferred-types/blob/master/src/types/boolean-logic/EndsWith.ts, https://github.com/inocan-group/inferred-types/blob/master/src/types/string-literals/StripLeading.ts Location: Package overview From: ? → npm/remark-cli@12.0.1 → npm/type-fest@3.13.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/type-fest@3.13.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		Potential code anomaly (AI signal): npm type-fest is 100.0% likely to have a medium risk anomaly Notes: This TypeScript utility file exports a compile-time type alias (IsNever) but also defines a runtime function endIfEqual(input, output) that calls process[.]exit(0) when the two strings are equal. Moreover, there is a top-level invocation of endIfEqual with identical strings, meaning merely importing or requiring the module will terminate the Node.js process. Embedding an unguarded process.exit in a library is highly unusual and can break downstream applications unexpectedly. It is recommended to remove or guard all runtime exit calls and ensure no side effects occur on module load. Confidence: 1.00 Severity: 0.60 From: ? → npm/remark-cli@12.0.1 → npm/type-fest@3.13.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/type-fest@3.13.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 undici-types URLs: https://mimesniff.spec.whatwg.org/#parse-a-mime-type, https://tools.ietf.org/html/rfc7230#section-6.3.2, https://fetch.spec.whatwg.org/#body-mixin, https://developer.mozilla.org/en-US/docs/Web/API/Blob, https://developer.mozilla.org/en-US/docs/Web/API/File Location: Package overview From: ? → npm/remark-cli@12.0.1 → npm/undici-types@5.26.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/undici-types@5.26.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		Embedded URLs or IPs: npm unified-message-control with options.name URLs: options.name Location: Package overview From: ? → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/unified-message-control@5.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/unified-message-control@5.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.
Warn		Embedded URLs or IPs: npm vfile URLs: file.data.name, https://nodejs.org/api/util.html#whatwg-supported-encodings Location: Package overview From: ? → npm/remark-frontmatter@5.0.0 → npm/remark-preset-lint-consistent@6.0.0 → npm/remark-preset-lint-recommended@7.0.0 → npm/remark-lint-no-shell-dollars@4.0.0 → npm/remark-preset-lint-markdown-style-guide@6.0.0 → npm/remark-cli@12.0.1 → npm/vfile@6.0.2 ℹ 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/vfile@6.0.2. 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 yaml URLs: https://caniuse.com/js-regexp-lookbehind, yaml.map, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#using_the_reviver_parameter Location: Package overview From: ? → npm/remark-cli@12.0.1 → npm/remark-lint-frontmatter-schema@3.15.4 → npm/yaml@2.3.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/yaml@2.3.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.
See 4 more rows in the dashboard

View full report