chore(deps): bump fast-xml-parser from 5.9.3 to 5.10.1 in /frontend

[dependabot]

Bumps fast-xml-parser from 5.9.3 to 5.10.1.

Release notes

Sourced from fast-xml-parser's releases.

v5.10.1

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.10.0...v5.10.1

v5.10.0

What's Changed

• Bump actions/checkout from 6.0.3 to 7.0.0 by @​dependabot[bot] in NaturalIntelligence/fast-xml-parser#849
• Bump zizmorcore/zizmor-action from 0.5.6 to 0.5.7 by @​dependabot[bot] in NaturalIntelligence/fast-xml-parser#848

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.9.3...v5.10.0

Changelog

Sourced from fast-xml-parser's changelog.

Note: If you find missing information about particular minor version, that version must have been changed without any functional change in this library.

Note: Due to some last quick changes on v4, detail of v4.5.3 & v4.5.4 are not updated here. v4.5.4x is the last tag of v4 in github repository. I'm extremely sorry for the confusion

5.10.1 / 2026-07-17

• fix: multiple DOCTYPE declarations.
• deps: @nodable/entities for treeshaking

5.10.0 / 2026-07-11

• upgrade:
  • xml-naming v0.3.0: cache support
  • PEM v1.6.2: sibling bug fix
  • is-unsafe v2.0.0: tree shaking

*5.9.3 / 2026-06-19

• update strnum

*5.9.2 / 2026-06-17

• dummy release to test changes in github action

*5.9.1 / 2026-06-17

• dummy release to test release from github action

*5.9.0 / 2026-06-15

• update strnum to 2.3.0
  • you can set hex, binary, enotation, infinity, unicode
• validate unsafe HTML or XML data in doctype entities unsing 'is-unsafe' library. User can override rules by overriding EntityDecoder.

*5.8.0 / 2026-05-12

• integrate xml-naming to validate DOCTYPE entity name and notation name (using qname becaue of backward compatibility)
  • This will consider xml-version as well. '1.0' is default
• update strnum to 2.3.0
  • You can set octal and binary parsing which is bydeault off
• update fast-xml-builder to 1.2.0
  • can sanitize tag names if found invalid
  • fix format output

5.7.3 / 2006-05-05

• fix: alwaysCreateTextNode should create text node when attributes are present for self closing node
• fix stop node expression when ns prefix is removed (found by iruizsalinas)
• update XML Builder to 1.1.7
• mark addEntity deprecated

5.7.2 / 2026-04-25

• allow numerical external entity for backward compatibility

... (truncated)

Commits

• 2ce7191 5.10.1
• 4e1bb01 update for release
• ffd1269 deps: @​nodable/entities for treeshaking
• 4e546e0 fix: multiple DOCTYPE are not allowed
• 296b332 5.10.0
• 75f7565 update package guide
• 2d8d1d0 update details
• e58e4dd upgrade: xml-naming v0.3.0, PEM v1.6.2, is-unsafe v2.0.0
• 545e491 Bump zizmorcore/zizmor-action from 0.5.6 to 0.5.7 (#848)
• 5ea8aa1 Bump actions/checkout from 6.0.3 to 7.0.0 (#849)
• 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 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.

[github-actions]

Latest scan for commit: 189e04b | Updated: 2026-07-24 08:25:11 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-07-24T08:24:54+00:00
• ASH version: 3.2.2

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	0	0	483ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	11.0s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	1.1s	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	4.8s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	395ms	0	PASSED	MED (g)
grype	0	0	0	3	0	0	57.8s	3	FAILED	MED (g)
npm-audit	0	0	0	0	0	0	185ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	19.9s	0	PASSED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	2.9s	0	PASSED	MED (g)

Detailed Findings

Show 3 actionable findings

Finding 1: GHSA-337j-9hxr-rhxg-react-router

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-337j-9hxr-rhxg-react-router
• Location: frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: react-router, version 6.30.4 was found at: /frontend/package-lock.json

---

Finding 2: GHSA-wrjc-x8rr-h8h6-react-router

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-wrjc-x8rr-h8h6-react-router
• Location: frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: react-router, version 6.30.4 was found at: /frontend/package-lock.json

---

Finding 3: GHSA-jjmj-jmhj-qwj2-react-router-dom

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-jjmj-jmhj-qwj2-react-router-dom
• Location: frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: react-router-dom, version 6.30.4 was found at: /frontend/package-lock.json

---

Report generated by Automated Security Helper (ASH) at 2026-07-24T08:24:50+00:00