Bump hono from 4.9.10 to 4.12.12 in /sample-dapps/rwa-tokenizer/frontend#401
Conversation
Bumps [hono](https://github.com/honojs/hono) from 4.9.10 to 4.12.12. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.9.10...v4.12.12) --- updated-dependencies: - dependency-name: hono dependency-version: 4.12.12 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 13c1c09. Configure here.
| natural-compare@1.4.0: | ||
| resolution: {integrity: sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==} | ||
|
|
||
| next@15.5.4: |
There was a problem hiding this comment.
Hono security fix not applied in pnpm lockfile
Medium Severity
The PR's stated goal is to bump hono from 4.9.10 to 4.12.12 for security fixes (middleware bypass, path traversal, IP restriction bypass, cookie vulnerabilities), but pnpm-lock.yaml still resolves hono to 4.9.10. Only package-lock.json was updated to 4.12.12. Since the project documents both npm and pnpm as valid package managers in its README, developers using pnpm will still install the vulnerable version of hono.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 13c1c09. Configure here.


Bumps hono from 4.9.10 to 4.12.12.
Release notes
Sourced from hono's releases.
... (truncated)
Commits
c37ba264.12.12cc067c8Merge commit from forka586cd7Merge commit from fork48fa223Merge commit from forkb470278Merge commit from fork9aff14bMerge commit from fork2c403c64.12.11f82aba8feat(css): add classNameSlug option to createCssContext (#4834)9f374a54.12.10a8c56a6docs(ip-restriction): add clear JSDoc examples and param types (#4851)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.
Note
Medium Risk
Dependency-only change, but it upgrades core runtime packages (
next,react,react-dom) alongsidehono, which could introduce subtle build/runtime regressions despite being patch releases.Overview
Upgrades
honoinsample-dapps/rwa-tokenizer/frontendfrom4.9.10to4.12.12.Regenerates
package-lock.jsonandpnpm-lock.yaml, which also pulls in patch bumps fornext(15.5.4->15.5.7) andreact/react-dom(19.1.0->19.1.2), plus associated transitive dependency reshuffling (e.g.,zoddeduping and additional Tailwind oxide WASM sub-deps).Reviewed by Cursor Bugbot for commit 13c1c09. Bugbot is set up for automated code reviews on this repo. Configure here.