chore(deps): bump @nodesecure/scanner from 10.12.0 to 10.13.0 in the dependencies group

[dependabot]

Bumps the dependencies group with 1 update: @nodesecure/scanner.

Updates @nodesecure/scanner from 10.12.0 to 10.13.0

Release notes

Sourced from @​nodesecure/scanner's releases.

@​nodesecure/scanner@​10.13.0

Minor Changes

• #735 f17981a Thanks @​clemgbld! - feat: extend contact with free email service flag

Patch Changes

• #741 53c60c1 Thanks @​fraxken! - Refactor highlight extractors to make them work in a web env. Add unit-test to scanner to ensure compatibility and CI break.

• Updated dependencies [53c60c1, f17981a]:

  • @​nodesecure/contact@​3.3.0
  • @​nodesecure/mama@​2.4.0
  • @​nodesecure/tree-walker@​4.0.2

Changelog

Sourced from @​nodesecure/scanner's changelog.

10.13.0

Minor Changes

• #735 f17981a Thanks @​clemgbld! - feat: extend contact with free email service flag

Patch Changes

• #741 53c60c1 Thanks @​fraxken! - Refactor highlight extractors to make them work in a web env. Add unit-test to scanner to ensure compatibility and CI break.

• Updated dependencies [53c60c1, f17981a]:

  • @​nodesecure/contact@​3.3.0
  • @​nodesecure/mama@​2.4.0
  • @​nodesecure/tree-walker@​4.0.2

Commits

• 4b182ad chore: update versions (#742)
• 52be58f chore: update versions (#738)
• 53c60c1 fix(scanner): ensure extractors are working in a web env (#741)
• f17981a feat: extend contact with free email service flag (#735)
• 0615c33 chore(deps-dev): bump @​types/node in the development-dependencies group (#736)
• 720e38c chore(deps): bump the dependencies group with 2 updates (#734)
• 4dae2cd fix(depWalker): bump ajv dependency in test fixtures (#732)
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​nodesecure/​scanner@​10.12.0 ⏵ 10.13.0				-3

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		Obfuscated code: npm @sigstore/tuf is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@nodesecure/scanner@10.13.0 → npm/@sigstore/tuf@5.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@sigstore/tuf@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.

View full report