Skip to content

chore(deps): bump fast-xml-parser and aws-amplify in /02-use-cases/A2A-multi-agent-incident-response/frontend#1174

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/02-use-cases/A2A-multi-agent-incident-response/frontend/multi-e195412944
Open

chore(deps): bump fast-xml-parser and aws-amplify in /02-use-cases/A2A-multi-agent-incident-response/frontend#1174
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/02-use-cases/A2A-multi-agent-incident-response/frontend/multi-e195412944

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 25, 2026

Bumps fast-xml-parser to 5.5.9 and updates ancestor dependency aws-amplify. These dependencies need to be updated together.

Updates fast-xml-parser from 4.4.1 to 5.5.9

Release notes

Sourced from fast-xml-parser's releases.

fix entity expansion and incorrect replacement and performance

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.5.5...v5.5.6

support onDangerousProperty

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.5.3...v5.5.5

update dependecies to fix typings

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.5.1...v5.5.2

integrate path-expression-matcher

  • support path-expression-matcher
  • fix: stopNode should not be parsed
  • performance improvement for stopNode checking

Separate Builder

XML Builder was the part of fast-xml-parser for years. But considering that any bug in builder may false-alarm the users who are only using parser and vice-versa, we have decided to split it into a separate package.

Migration

To migrate to fast-xml-builder;

From

import { XMLBuilder } from "fast-xml-parser";

To

import  XMLBuilder  from "fast-xml-builder";

XMLBuilder will be removed from current package in any next major version of this library. So better to migrate.

support strictReservedNames

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

handle non-array input for XML builder && support maxNestedTags

CJS typing fix

What's Changed

New Contributors

... (truncated)

Commits

Updates aws-amplify from 6.15.8 to 6.16.3

Release notes

Sourced from aws-amplify's releases.

aws-amplify@6.16.3

Patch Changes

  • Updated dependencies [e2b77fa]:
    • @​aws-amplify/storage@​6.13.2

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

2026-02-05 Amplify JS release - aws-amplify@6.16.2

What's Changed

Full Changelog: https://github.com/aws-amplify/amplify-js/compare/aws-amplify@6.16.0...aws-amplify@6.16.2

2026-02-02 Amplify JS release - aws-amplify@6.16.1

No change.

2026-01-23 Amplify JS release - aws-amplify@6.16.0

What's Changed

Full Changelog: https://github.com/aws-amplify/amplify-js/compare/aws-amplify@6.15.10...aws-amplify@6.16.0

2026-01-15 Amplify JS release - aws-amplify@6.15.10

What's Changed

... (truncated)

Commits

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.

@dependabot
chore(deps): bump fast-xml-parser and aws-amplify
993928a 
Bumps [fast-xml-parser](https://github.com/NaturalIntelligence/fast-xml-parser) to 5.5.9 and updates ancestor dependency [aws-amplify](https://github.com/aws-amplify/amplify-js). These dependencies need to be updated together.


Updates `fast-xml-parser` from 4.4.1 to 5.5.9
- [Release notes](https://github.com/NaturalIntelligence/fast-xml-parser/releases)
- [Changelog](https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md)
- [Commits](https://github.com/NaturalIntelligence/fast-xml-parser/commits)

Updates `aws-amplify` from 6.15.8 to 6.16.3
- [Release notes](https://github.com/aws-amplify/amplify-js/releases)
- [Commits](https://github.com/aws-amplify/amplify-js/compare/aws-amplify@6.15.8...aws-amplify@6.16.3)

---
updated-dependencies:
- dependency-name: fast-xml-parser
  dependency-version: 5.5.9
  dependency-type: indirect
- dependency-name: aws-amplify
  dependency-version: 6.16.3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 25, 2026
@github-actions github-actions bot added the 02-use-cases 02-use-cases label Mar 25, 2026
@github-actions
Copy link

github-actions bot commented Mar 25, 2026

Latest scan for commit: 993928a | Updated: 2026-03-25 19:53:58 UTC

Security Scan Results

Scan Metadata

  • Project: ASH
  • Scan executed: 2026-03-25T19:53:45+00:00
  • ASH version: 3.0.0

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 424ms 0 PASSED MED (g)
cdk-nag 0 0 0 0 0 0 33.0s 0 PASSED MED (g)
cfn-nag 0 0 0 0 0 0 713ms 0 PASSED MED (g)
checkov 0 0 0 0 0 0 4.7s 0 PASSED MED (g)
detect-secrets 0 0 0 0 0 0 1.1s 0 PASSED MED (g)
grype 0 3 0 1 0 0 34.9s 4 FAILED MED (g)
npm-audit 0 0 0 0 0 0 995ms 0 PASSED MED (g)
opengrep 0 0 0 0 0 0 <1ms 0 SKIPPED MED (g)
semgrep 0 0 0 0 0 0 18.2s 0 PASSED MED (g)
syft 0 0 0 0 0 0 2.0s 0 PASSED MED (g)

Detailed Findings

Show 4 actionable findings

Finding 1: GHSA-xxjr-mmjv-4gpg-lodash

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-xxjr-mmjv-4gpg-lodash
  • Location: 02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: lodash, version 4.17.21 was found at: /02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json

Finding 2: GHSA-3ppc-4f35-3m26-minimatch

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-3ppc-4f35-3m26-minimatch
  • Location: 02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 9.0.5 was found at: /02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json

Finding 3: GHSA-7r86-cg39-jmmj-minimatch

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-7r86-cg39-jmmj-minimatch
  • Location: 02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 9.0.5 was found at: /02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json

Finding 4: GHSA-23c5-xmqv-rm74-minimatch

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-23c5-xmqv-rm74-minimatch
  • Location: 02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 9.0.5 was found at: /02-use-cases/A2A-multi-agent-incident-response/frontend/package-lock.json

Report generated by Automated Security Helper (ASH) at 2026-03-25T19:53:40+00:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

02-use-cases 02-use-cases dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants