Skip to content
Open
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -295,11 +295,11 @@
"lowlight": "3.1.0",
"markdownlint-rule-helpers": "^0.25.0",
"mdast-util-from-markdown": "^2.0.0",
"mdast-util-to-hast": "^13.2.0",
"mdast-util-to-hast": "^13.2.1",
"mdast-util-to-markdown": "2.1.0",
"mdast-util-to-string": "^4.0.0",
"morgan": "^1.10.0",
"next": "^15.1.5",
"next": "^15.1.9",
Comment on lines +298 to +302

Choose a reason for hiding this comment

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

critical

As noted in the pull request description, package-lock.json has not been updated to reflect the dependency changes in package.json. This is a critical issue, as it means the vulnerable package versions might still be used.

Please run npm install to update package-lock.json and commit the changes before merging.

Comment on lines +298 to +302

Choose a reason for hiding this comment

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

P1 Badge Update lockfile to match bumped dependency versions

The change raises mdast-util-to-hast to ^13.2.1 and next to ^15.1.9 in package.json (lines 298‑302), but package-lock.json still pins mdast-util-to-hast to ^13.2.0 and next to ^15.1.5 (e.g., lines 67 and 71). Any install path that honors the lockfile (npm ci/install) will continue to pull the old vulnerable versions, so the intended security fix never takes effect. Please regenerate the lockfile to align with the updated package versions.

Useful? React with 👍 / 👎.

"ora": "^8.0.1",
"parse5": "7.1.2",
"quick-lru": "7.0.0",
Expand Down