Skip to content

fix: [Vulns #2,6,8] upgrade tap 11.x → 18.x to resolve 3 critical transitive dependency CVEs#23

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1780066162-fix-tap-transitive-deps
Open

fix: [Vulns #2,6,8] upgrade tap 11.x → 18.x to resolve 3 critical transitive dependency CVEs#23
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1780066162-fix-tap-transitive-deps

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented May 29, 2026

Copy link
Copy Markdown

Summary

Upgrades tap from ^11.1.3 to ^18.0.0 to resolve 3 critical transitive dependency CVEs:

Vuln # CVE Package Severity
#2 CVE-2025-7783 form-data@2.3.3 CRITICAL
#6 CVE-2025-9288 sha.js@2.4.11 CRITICAL
#8 CVE-2023-45133 babel-traverse@6.26.0 CRITICAL

All three packages were transitive dependencies pulled in through tap@11.x. After upgrading to tap@18.x:

  • form-data@2.3.3 — no longer in the dependency tree
  • babel-traverse@6.26.0 — no longer in the dependency tree
  • sha.js@2.4.11 — no longer pulled through tap (remaining instances come from browserify and typeorm)

Files changed: package.json, package-lock.json

Review & Testing Checklist for Human

Notes

  • tap is listed under dependencies rather than devDependencies in this repo. The upgrade is scoped only to the tap version — no application code changes were needed.
  • sha.js@2.4.11 still appears via browserify and typeorm — those are separate dependency paths unrelated to this fix.

Link to Devin session: https://app.devin.ai/sessions/d44b2a02e84f46e7874d5ac33659836c
Requested by: @jakejluo


Devin Review

Status Commit
⚪ Not started

Run Devin Review

💡 Connect your GitHub account to enable automatic code reviews.

Open in Devin Review (Staging)

…nsitive dependency CVEs

Co-Authored-By: Jake Luo <jake.luo@cognition.ai>
@devin-ai-integration

Copy link
Copy Markdown
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

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