Patch hono, qs and js-yaml, the three packages behind the open advisories - #15
Merged
Merged
Conversation
…ries All three are transitive and each was one patch release away from the fix: hono 4.13.4 -> 4.13.9, qs 6.15.3 -> 6.16.0, js-yaml 4.3.1 -> 4.3.2. That closes six Dependabot alerts (one high, five medium). The grouped version bump in #14 does not touch any of them, because it only moves direct dependencies. The lockfile also loses a handful of "peer": true markers. That is npm 11 normalising the file; no resolved version changes besides the three above. npm audit --omit=dev: 0 vulnerabilities. npm run verificar: approved.
Navesz
force-pushed
the
patch-runtime-advisories
branch
from
September 24, 2026 17:08
9136af9 to
95635fe
Compare
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
1 participant
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.
Closes the six open Dependabot alerts on
main(1 high, 5 moderate).honoqsjs-yamlAll three are transitive. The grouped bump in #14 does not reach them because it only moves direct dependencies, which is why the alerts stayed open next to it.
The lockfile also drops a few
"peer": truemarkers — npm 11 normalising the file. No resolved version changes besides the three above.Checked locally
npm audit --omit=dev→ 0 vulnerabilitiesnpm run verificar→ approved (instrucoes · formato · controle · segredo · elos · tipos · lint · fronteiras · testes · build)