Skip to content

chore(deps-dev): bump picomatch from 2.3.1 to 2.3.2 in /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack#1222

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/picomatch-2.3.2
Open

chore(deps-dev): bump picomatch from 2.3.1 to 2.3.2 in /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack#1222
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/picomatch-2.3.2

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

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

Bumps picomatch from 2.3.1 to 2.3.2.

Release notes

Sourced from picomatch's releases.

2.3.2

This is a security release fixing several security relevant issues.

What's Changed

Full Changelog: micromatch/picomatch@2.3.1...2.3.2

Changelog

Sourced from picomatch's changelog.

Release history

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

  • Changelogs are for humans, not machines.
  • There should be an entry for every single version.
  • The same types of changes should be grouped.
  • Versions and sections should be linkable.
  • The latest version comes first.
  • The release date of each versions is displayed.
  • Mention whether you follow Semantic Versioning.

Changelog entries are classified using the following labels (from keep-a-changelog):

  • Added for new features.
  • Changed for changes in existing functionality.
  • Deprecated for soon-to-be removed features.
  • Removed for now removed features.
  • Fixed for any bug fixes.
  • Security in case of vulnerabilities.

4.0.0 (2024-02-07)

Fixes

Changed

3.0.1

Fixes

... (truncated)

Commits

Dependabot compatibility score

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-dev): bump picomatch
85900df 
Bumps [picomatch](https://github.com/micromatch/picomatch) from 2.3.1 to 2.3.2.
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@2.3.1...2.3.2)

---
updated-dependencies:
- dependency-name: picomatch
  dependency-version: 2.3.2
  dependency-type: indirect
...

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 30, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 30, 2026

Latest scan for commit: 85900df | Updated: 2026-03-30 12:59:10 UTC

Security Scan Results

Scan Metadata

  • Project: ASH
  • Scan executed: 2026-03-30T12:58:56+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 660ms 0 PASSED MED (g)
cdk-nag 0 0 0 0 0 0 31.8s 0 PASSED MED (g)
cfn-nag 0 0 0 0 0 0 242ms 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 744ms 0 PASSED MED (g)
grype 0 3 0 3 0 0 38.8s 6 FAILED MED (g)
npm-audit 0 0 0 0 0 0 159ms 0 PASSED MED (g)
opengrep 0 0 0 0 0 0 <1ms 0 SKIPPED MED (g)
semgrep 0 0 0 0 0 0 15.1s 0 PASSED MED (g)
syft 0 0 0 0 0 0 2.2s 0 PASSED MED (g)

Detailed Findings

Show 6 actionable findings

Finding 1: GHSA-f886-m6hf-6m8v-brace-expansion

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-f886-m6hf-6m8v-brace-expansion
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A medium vulnerability in npm package: brace-expansion, version 1.1.12 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

Finding 2: GHSA-48c2-rrv3-qjmp-yaml

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-48c2-rrv3-qjmp-yaml
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A medium vulnerability in npm package: yaml, version 1.10.2 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

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

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-3ppc-4f35-3m26-minimatch
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 3.1.2 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

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

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-7r86-cg39-jmmj-minimatch
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 3.1.2 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

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

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-23c5-xmqv-rm74-minimatch
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A high vulnerability in npm package: minimatch, version 3.1.2 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

Finding 6: GHSA-2g4f-4pwh-qvx6-ajv

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-2g4f-4pwh-qvx6-ajv
  • Location: 05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json:1

Description:
A medium vulnerability in npm package: ajv, version 8.17.1 was found at: /05-blueprints/travel-concierge-agent/infrastructure/visa-lambda-stack/package-lock.json

Report generated by Automated Security Helper (ASH) at 2026-03-30T12:58:50+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

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