Skip to content

fix(deps): bump hono for audit compliance #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ndycode merged 1 commit into from
Mar 10, 2026
Merged

fix(deps): bump hono for audit compliance #67

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,11 +118,11 @@
"dependencies": {
"@openauthjs/openauth": "^0.4.3",
"@codex-ai/plugin": "file:vendor/codex-ai-plugin",
"hono": "4.12.3",
"hono": "4.12.6",
"zod": "^4.3.6"
},
"overrides": {
"hono": "4.12.3",
"hono": "4.12.6",
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

exact override pin blocks future security patches. "hono": "4.12.6" forces any transitive consumer back to 4.12.6, even if a patch like 4.12.7 is released. if another CVE lands in hono before the next dep PR, this override actively blocks the fix.

consider ">=4.12.6" instead — allows future patches while enforcing the minimum security version:

Suggested change
"hono": "4.12.6",
"hono": ">=4.12.6",
Prompt To Fix With AI 
This is a comment left during a code review.
Path: package.json
Line: 125

Comment:
exact override pin blocks future security patches. `"hono": "4.12.6"` forces any transitive consumer back to 4.12.6, even if a patch like 4.12.7 is released. if another CVE lands in hono before the next dep PR, this override actively blocks the fix.

consider `">=4.12.6"` instead — allows future patches while enforcing the minimum security version:

```suggestion
    "hono": ">=4.12.6",
```

How can I resolve this? If you propose a fix, please make it concise.

Fix in Codex

"minimatch": "10.2.4",
"rollup": "4.59.0",
"vite": "^7.3.1",
Expand Down