chore(deps): bump js-yaml from 3.13.1 to 3.15.2

[dependabot]

Bumps js-yaml from 3.13.1 to 3.15.2.

Changelog

Sourced from js-yaml's changelog.

3.15.2 - 2026-08-26

Changed

• [backport] Hard-limit merge sequence size to 100.

Security

• [backport] Count empty mappings in merge sequences toward maxTotalMergeKeys to limit CPU usage, #797.

3.15.1 - 2026-07-31

Security

• [backport] Remove quadratic complexity from !!omap duplicate key detection.

3.15.0 - 2026-06-27

Added

• Added maxTotalMergeKeys (10000) loader option to limit the total number of keys processed by YAML merge (<<) across one safeLoad() / safeLoadAll() call.

[3.14.2] - 2025-11-15

Security

• Fix prototype pollution in merge (<<).

[3.14.1] - 2020-12-07

Security

• Fix possible code execution in (already unsafe) .load() (in &anchor).

[3.14.0] - 2020-05-22

Changed

• Support safe/loadAll(input, options) variant of call.
• CI: drop outdated nodejs versions.
• Dev deps bump.

Fixed

• Quote = in plain scalars #519.
• Check the node type for !<?> tag in case user manually specifies it.
• Verify that there are no null-bytes in input.
• Fix wrong quote position when writing condensed flow, #526.

Commits

• 5c45bd6 3.15.2 released
• 5a708f9 dist rebuild
• 3485bc0 Backport merge limits from v5.4.1
• f34812f Update .gitignore
• ab85ae2 3.15.1 released
• 30a5e76 dist rebuild
• 22a8071 Backport quadratic complexity fix for !!omap
• c34b6c4 3.15.0 released
• 21e13d3 dist rebuild
• 4165c62 Add v3-legacy tag for publish
• 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.

[linkorb-automation]

Security-Reviewed-Head-SHA: c4ad4cb
Reviewed head SHA: c4ad4cb
Security scope only: this is not a full functional approval.

✅ Security review: thumbs up / no security concerns found

Security review

Verdict: SECURITY_APPROVE

I reviewed this PR's diff and dependency impact from a security perspective. The PR changes only package-lock.json; there are no application-code, CI/GitHub Actions, Docker/infrastructure, auth, file-handling, or logging changes.

Security checks performed:

• Confirmed the only package version change is js-yaml from 3.13.1 to 3.15.2; the rest of the large diff is lockfile v1 -> v3 structural churn.
• Verified js-yaml@3.15.2 registry metadata matches the lockfile tarball/integrity.
• Confirmed js-yaml is a dev-only transitive dependency under husky -> cosmiconfig.
• Compared audit output: the base lockfile had a js-yaml vulnerability entry and 40 total findings; this PR removes the js-yaml finding and reports 39 total findings. Remaining audit findings appear pre-existing and unrelated to this PR.

Checklist coverage: secrets/credentials, authn/authz bypass, injection, XSS/CSRF, SSRF, path traversal, unsafe deserialization, crypto/TLS/session issues, dependency/version risk, CI/CD privilege escalation, Docker/infrastructure exposure, sensitive logging, access-control regressions, unsafe upload/download, and multi-tenant isolation were considered. No PR-introduced blocking security issues were found.