Repository navigation
fix(deps): refresh the lockfile to hono 4.13.13 - #1171
Merged
Merged
Conversation
GHSA-5r4p-p66f-jhc7 (moderate): hono's serveStatic decodes the request path a second time, so middleware on static paths can be bypassed. Versions 4.12.4 to 4.13.10 are affected and main pins 4.13.9 through tuistory, which release packaging installs as a local-control helper. npm update takes hono to 4.13.13, inside every range that asks for it. package.json is unchanged and nothing else in the lock moves.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
Zero automated PR reviewVerdict: No blockers found Blockers
Validation
ScopeHead: This deterministic review checks validation status and basic diff hygiene. A human reviewer still owns product judgment and design quality. |
kevincodex1
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refreshes
package-lock.jsonsohonomoves from 4.13.9 to 4.13.13, inside every range that asks for it (tuistory^4.11.7,@hono/node-ws^4.6.0,@hono/node-server^4).package.jsonis unchanged and nothing else in the lock moves. 4.13.11 is the first patched release;npm updatetook the newest 4.13.x.Why
Dependabot alert 11 opened on
maintoday for GHSA-5r4p-p66f-jhc7 (CVE-2026-111757, moderate):hono'sserveStaticdecodes the request path a second time, so middleware on static paths can be bypassed.honocomes in throughtuistory, which release packaging installs as a local-control helper, the same route as #1080. I have not checked whethertuistoryreachesserveStatic. Either way, this moves the helper tree we ship off the flagged range.Verification
npm audit --package-lock-only --omit=dev: 0 vulnerabilities, against 1 moderate (this advisory) onmain.npm ls --all --package-lock-only --omit=dev: the tree resolves. The only UNMET lines are the five optional peersmainalready has.agent-browser ^0.30.1andtuistory ^0.10.0, copies this lock beside it and runsnpm ci --omit=dev. That pair passesnpm ci --omit=dev --dry-run --ignore-scripts.node --test scripts/action-summary.test.mjs: 12 of 12.go vet ./...for windows, linux and darwin,go test ./...,go run ./cmd/zero-release buildandsmoke, andgovulncheck ./...all pass on Windows.Not run: the real helper staging in
zero-release package, which installs the packages and runs their install scripts. Onlyrelease-artifacts.ymldoes that, so a maintainer can dispatch it with this branch asreffor the shim check on every platform.