test(deps): bump @types/node from 26.3.0 to 26.4.0 in the npm group across 1 directory

[dependabot]

Bumps the npm group with 1 update in the / directory: @types/node.

Updates @types/node from 26.3.0 to 26.4.0

Commits

• 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

[github-actions]

✅⚠️MegaLinter analysis: Success with warnings

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ ACTION	actionlint	24		0		0	0.53s
✅ ACTION	zizmor	24	0	0		0	5.82s
✅ DOCKERFILE	hadolint	3		0		0	1.14s
✅ JSON	npm-package-json-lint	yes		no		no	0.51s
✅ JSON	prettier	22	3	0		0	1.02s
✅ JSON	v8r	22		0		0	9.79s
✅ MARKDOWN	markdownlint	12	0	0		0	1.39s
✅ MARKDOWN	markdown-table-formatter	12	1	0		0	0.26s
✅ REPOSITORY	betterleaks	yes		no		no	1.16s
✅ REPOSITORY	checkov	yes		no		no	21.51s
✅ REPOSITORY	git_diff	yes		no		no	0.06s
✅ REPOSITORY	grype	yes		no		no	74.74s
✅ REPOSITORY	osv-scanner	yes		no		no	1.52s
✅ REPOSITORY	secretlint	yes		no		no	2.27s
✅ REPOSITORY	syft	yes		no		no	4.1s
✅ REPOSITORY	trivy	yes		no		no	11.6s
✅ REPOSITORY	trivy-sbom	yes		no		no	0.36s
✅ REPOSITORY	trufflehog	yes		no		no	5.06s
⚠️ SPELL	lychee	86		1		0	10.75s
✅ YAML	prettier	32	0	0		0	1.05s
✅ YAML	v8r	32		0		0	10.43s
✅ YAML	yamllint	32		0		0	1.3s

Detailed Issues

⚠️ SPELL / lychee - 1 error

📝 Summary
---------------------
🔍 Total..........133
🔗 Unique.........112
✅ Successful.....127
⏳ Timeouts.........0
🔀 Redirected......13
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........1
⛔ Unsupported......1

Errors in .github/TOOL_VERSION_ISSUE_TEMPLATE.md
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads (at 30:7) | Rejected status code: 403 Forbidden

Hint: Followed 13 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
Hint: You can configure accepted/rejected response codes with `-a` or `--accept`

Notices

⚠️ Your configuration references items that have been removed from MegaLinter and are ignored: REPOSITORY_KICS. See Removed linters to find their replacements.

See detailed reports in MegaLinter artifacts

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/salesforce@v10.0.0 (57 linters)
• oxsecurity/megalinter/flavors/javascript@v10.0.0 (62 linters)

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@10.0.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,ACTION_ZIZMOR,DOCKERFILE_HADOLINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository

[github-actions]

Pull Request Report (#120)

Static measures

Description	Value
Number of added lines	5
Number of deleted lines	5
Number of changed files	2
Number of commits	1
Number of reviews	0
Number of comments (w/o review comments)	1
Number of reviews that contains a comment to resolve	0
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	0
Get the total number of participants of a Pull Request	2

Time related measures

Description	Value
PR lead time (from creation to close of PR)	19.6 Min
Time that was spend on the branch before the PR was created	1 Sec
Time that was spend on the branch before the PR was merged	19.6 Min
Time to merge after last review	0 Sec

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	11.3 Min
Total time spend in last status check run on PR	4.1 Min