Skip to content

fix(deps): update node-forge lockfile for security advisories - #17

Merged
ChiragAgg5k merged 1 commit into
mainfrom
fix-node-forge-lockfile
Nov 14, 2026
Merged

ChiragAgg5k merged 1 commit into
mainfrom
fix-node-forge-lockfile

Conversation

@ChiragAgg5k

@ChiragAgg5k ChiragAgg5k commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Lockfile-only bump (no package.json changes). Follow-up to #16, after which Dependabot reopened node-forge alerts for nitropack > listhen.

Package Old New Advisories
node-forge 1.4.2 1.4.3 GHSA-6889-vf6x-f3g5, GHSA-w4xr-hqv8-ch44, GHSA-6cv4-p8m7-4r25, GHSA-j8rw-jp99-435v

Verified with npm ci --ignore-scripts and npm run build.

Related: appwrite-labs/cloud#6671

@appwrite

appwrite Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

🟢 Tier S · Ready to merge

The locked install and production build succeed, and the application does not call node-forge APIs directly.

The lockfile updates the transitive node-forge dependency used by listhen from 1.4.2 to 1.4.3. No application code or package manifest changes are included.

Verdict New comments Fixed Still open
✅ Approved 0 0 0
📂 Walkthrough · 1
File Change
package-lock.json Pins the resolved node-forge package to 1.4.3.

Reviewed 75227c4 · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Tier S · Looks good to merge. Summary

@ChiragAgg5k
ChiragAgg5k merged commit b24d10b into main Nov 14, 2026
2 checks passed
@ChiragAgg5k
ChiragAgg5k deleted the fix-node-forge-lockfile branch November 14, 2026 00:13
@ChiragAgg5k ChiragAgg5k self-assigned this Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant