Skip to content

chore(deps-dev): bump hono from 4.12.26 to 4.12.32 in /samples/dual-monitoring-system/frontend - #135

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/dual-monitoring-system/frontend/hono-4.12.32
Open

chore(deps-dev): bump hono from 4.12.26 to 4.12.32 in /samples/dual-monitoring-system/frontend#135
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/dual-monitoring-system/frontend/hono-4.12.32

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 28, 2026

Copy link
Copy Markdown
Contributor

Bumps hono from 4.12.26 to 4.12.32.

Release notes

Sourced from hono's releases.

v4.12.32

What's Changed

  • ci: enable reports for type & bundle size check in honojs/hono#5148
  • fix(aws-lambda): add jwt and lambda authorizer types for API Gateway v2 in honojs/hono#5142
  • fix(sse): emit empty id field to reset Last-Event-ID in honojs/hono#5138
  • test(cloudflare-workers): add coverage for onClose, onError, send, and close in Cloudflare Workers websocket adapter in honojs/hono#5145
  • fix: use Object.create(null) when parsing query, headers, and params in honojs/hono#5161
  • fix(secure-headers): keep CSP callbacks scoped to their header in honojs/hono#5147

Full Changelog: honojs/hono@v4.12.31...v4.12.32

v4.12.31

What's Changed

Full Changelog: honojs/hono@v4.12.30...v4.12.31

v4.12.30

What's Changed

Full Changelog: honojs/hono@v4.12.29...v4.12.30

v4.12.29

What's Changed

New Contributors

... (truncated)

Commits
  • 26d8e42 4.12.32
  • 402eb3a fix(secure-headers): keep CSP callbacks scoped to their header (#5147)
  • c85aead fix: use Object.create(null) when parsing query, headers, and params (#5161)
  • a88c89d test(cloudflare-workers): add coverage for onClose, onError, send, and close ...
  • 44f8843 fix(sse): emit empty id field to reset Last-Event-ID (#5138)
  • e36f57d fix(aws-lambda): add jwt and lambda authorizer types for API Gateway v2 (#5142)
  • bf8608c ci: enable reports for type & bundle size check (#5148)
  • cadff88 4.12.31
  • 64c613a test(validator): fix misspelled identifier in transform type test (#5136)
  • aeba9ec fix(sse): emit retry feild when retry is 0 (#5135)
  • Additional commits viewable in compare view

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 hono in /samples/dual-monitoring-system/frontend
acec989 
Bumps [hono](https://github.com/honojs/hono) from 4.12.26 to 4.12.32.
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.12.26...v4.12.32)

---
updated-dependencies:
- dependency-name: hono
  dependency-version: 4.12.32
  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 Jul 28, 2026
@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown

Latest scan for commit: acec989 | Updated: 2026-07-28 05:19:20 UTC

Security Scan Results

Scan Metadata

  • Project: ASH
  • Scan executed: 2026-07-28T05:19:02+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 596ms 0 PASSED MED (g)
cdk-nag 0 0 0 0 0 0 6.9s 0 PASSED MED (g)
cfn-nag 0 0 0 0 0 0 590ms 0 PASSED MED (g)
checkov 0 0 0 0 0 0 4.3s 0 PASSED MED (g)
detect-secrets 0 0 0 0 0 0 109ms 0 PASSED MED (g)
grype 0 3 0 2 0 0 46.5s 5 FAILED MED (g)
npm-audit 0 0 0 0 0 0 147ms 0 PASSED MED (g)
opengrep 0 0 0 0 0 0 15.7s 0 PASSED MED (g)
semgrep 0 0 0 0 0 0 <1ms 0 MISSING MED (g)
syft 0 0 0 0 0 0 2.3s 0 PASSED MED (g)

Detailed Findings

Show 5 actionable findings

Finding 1: GHSA-w5hq-g745-h8pq-uuid

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-w5hq-g745-h8pq-uuid
  • Location: samples/dual-monitoring-system/frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: uuid, version 11.1.0 was found at: /samples/dual-monitoring-system/frontend/package-lock.json

Finding 2: GHSA-qx2v-qp2m-jg93-postcss

  • Severity: MEDIUM
  • Scanner: grype
  • Rule ID: GHSA-qx2v-qp2m-jg93-postcss
  • Location: samples/dual-monitoring-system/frontend/package-lock.json:1

Description:
A medium vulnerability in npm package: postcss, version 8.4.31 was found at: /samples/dual-monitoring-system/frontend/package-lock.json

Finding 3: GHSA-6g55-p6wh-862q-postcss

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-6g55-p6wh-862q-postcss
  • Location: samples/dual-monitoring-system/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: postcss, version 8.4.31 was found at: /samples/dual-monitoring-system/frontend/package-lock.json

Finding 4: GHSA-r28c-9q8g-f849-postcss

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-r28c-9q8g-f849-postcss
  • Location: samples/dual-monitoring-system/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: postcss, version 8.4.31 was found at: /samples/dual-monitoring-system/frontend/package-lock.json

Finding 5: GHSA-f88m-g3jw-g9cj-sharp

  • Severity: HIGH
  • Scanner: grype
  • Rule ID: GHSA-f88m-g3jw-g9cj-sharp
  • Location: samples/dual-monitoring-system/frontend/package-lock.json:1

Description:
A high vulnerability in npm package: sharp, version 0.34.5 was found at: /samples/dual-monitoring-system/frontend/package-lock.json

Report generated by Automated Security Helper (ASH) at 2026-07-28T05:18:54+00:00

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

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file frontend 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