chore(deps): bump @nodesecure/js-x-ray from 11.2.0 to 11.3.0 in the dependencies group

[dependabot]

Bumps the dependencies group with 1 update: @nodesecure/js-x-ray.

Updates @nodesecure/js-x-ray from 11.2.0 to 11.3.0

Release notes

Sourced from @​nodesecure/js-x-ray's releases.

@​nodesecure/js-x-ray@​11.3.0

Minor Changes

• #453 0b0751a Thanks @​clemgbld! - feat(js-x-ray): scan and collect ip address that are not urls

• #452 a01b8e7 Thanks @​7amed3li! - Added detection for local IP addresses and localhost in URLs. These are now flagged with the existing shady-link warning but with Information severity level instead of Warning.

• #450 3185318 Thanks @​fraxken! - Allow to customize warnings severity

Changelog

Sourced from @​nodesecure/js-x-ray's changelog.

11.3.0

Minor Changes

• #453 0b0751a Thanks @​clemgbld! - feat(js-x-ray): scan and collect ip address that are not urls

• #452 a01b8e7 Thanks @​7amed3li! - Added detection for local IP addresses and localhost in URLs. These are now flagged with the existing shady-link warning but with Information severity level instead of Warning.

• #450 3185318 Thanks @​fraxken! - Allow to customize warnings severity

Commits

• 124610a chore: update versions (#451)
• 0b0751a feat(js-x-ray): scan and collect ip address that are not urls (#453)
• a01b8e7 feat: implement shady-url detection for local IPs and localhost (#449) (#452)
• 3185318 chore(generateWarning): allow to customize/override warning severity
• ce92acd fix(test/ProbeRunner): properly type and implement CollectableRegistry
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 408560d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​changesets/​changelog-github@​0.5.2
	@​types/​object-hash@​3.0.6
	@​openally/​config.typescript@​1.2.1
	@​openally/​config.eslint@​2.2.0
	@​nodesecure/​js-x-ray@​11.2.0 ⏵ 11.3.0	+1		+1	+1
	@​types/​node@​24.10.1
	get-folder-size@​5.0.0
	@​arethetypeswrong/​cli@​0.18.2
	@​changesets/​cli@​2.29.8

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		License policy violation: npm @tsd/typescript License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/typescript/ThirdPartyNoticeText.txt) From: ? → npm/@tsd/typescript@5.9.3 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@tsd/typescript@5.9.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		License policy violation: npm typescript License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) From: ? → npm/@arethetypeswrong/cli@0.18.2 → npm/typescript@5.6.1-rc ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.6.1-rc. 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