Repository navigation
fix(deps): bump transitive hono 4.12.23 -> 4.12.28 in lockfile - #1
Merged
Merged
Conversation
hono <4.12.26 carries a high-severity CORS wildcard-reflection advisory plus four medium ones (path traversal, Lambda header handling). The pin comes transitively via @modelcontextprotocol/sdk under the cortex-engine devDependency, so this only affects contributor/CI installs — the published package is unaffected. Dependabot never surfaced an alert for this repo (stale dependency graph); this push should also force a rescan. Verified: npm audit clean (0 vulnerabilities), tsc build green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Why
npm auditon a fresh clone flags 1 high-severity advisory: hono <4.12.26 reflects any Origin with credentials when CORSorigindefaults to the wildcard (plus four medium advisories — Windows path traversal inserve-static, Lambda header/cookie handling, body-limit bypass).The vulnerable pin (4.12.23) enters transitively:
@fozikio/cortex-engine(devDependency) →@modelcontextprotocol/sdk→hono ^4.11.4. The SDK's range already allows the patched version, so this is a lockfile-only refresh — no package.json change, no version bump, no publish needed. Consumers of the published@fozikio/tools-graphpackage were never exposed (lockfiles don't ship; the package has only peerDeps).Note: Dependabot has never generated an alert for this repo despite vulnerability alerts being enabled — the dependency graph appears stale. This push should also force GitHub to rescan it.
Verification
npm audit: 0 vulnerabilities (was 1 high)npm run build(tsc): cleanpackage-lock.json(hono 4.12.23 → 4.12.28)🤖 Generated with Claude Code