Multiple security vulnerabilities in transitive dependencies
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 3
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 7
Description
Summary
@vis.gl/dev-tools@1.0.1 has multiple high and critical severity vulnerabilities in its transitive dependency tree. These affect all downstream consumers (including deck.gl-community).
Vulnerabilities
| Package | Severity | Advisory | Via |
|---|---|---|---|
form-data < 2.5.4 |
critical | GHSA-fjxv-7rqg-78g4 | coveralls -> request |
axios <= 1.13.4 |
high | GHSA-43fc-jf86-j433 | lerna -> nx |
tar <= 7.5.2 (3 CVEs) |
high | GHSA-4r9x-wfcq-p4qr, GHSA-9pj4-f7r4-9m3v, GHSA-jppv-jxq6-24cw | lerna |
qs < 6.14.1 |
high | GHSA-hx3m-959f-v3r5 | coveralls -> request |
trim < 0.0.3 |
high | GHSA-w5p7-h5w8-2hfq | tap-spec -> tap-out |
glob 10.x/11.x (2 CVEs) |
high | GHSA-rsm9-g255-8vv4 | lerna -> @npmcli |
cross-spawn < 6.0.6 |
high | GHSA-3xgq-45jj-v275 | various |
esbuild <= 0.24.2 |
moderate | GHSA-67mh-4wv8-2f99 | direct dep (^0.16.7) |
eslint 8.x |
moderate | deprecated | direct dep |
Root cause dependencies in dev-tools
These are the direct dependencies that pull in the vulnerable packages:
coveralls: ^3.0.3-- pulls inrequestwhich pulls inform-data,qs, etc.lerna: ^8.1.0-- pulls innx(axios),tar,globtap-spec: ^5.0.0-- pulls intap-out->trimesbuild: ^0.16.7-- outdated, current is 0.25.xeslint: ^8.52.0-- deprecated, current is 9.xvite: ^4.5.0-- outdated, current is 7.x
Suggested fixes
- Drop
coveralls-- it depends on the abandonedrequestpackage. Modern alternatives:codecovor GitHub Actions coverage reporting - Bump
lernato latest or consider replacing withturbo/nxdirectly - Drop
tap-spec-- replace with vitest or another modern test reporter - Bump
esbuildto^0.25.0 - Bump
eslintto 9.x with flat config - Bump
viteto^7.3.1
Context
Found during a security audit of visgl/deck.gl-community. The 1.0.0-alpha.21 and 1.0.1 releases have identical dependency trees, so bumping dev-tools alone does not resolve these.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the direct dependencies listed in the issue and run the dependency audit to confirm the vulnerable transitive packages and their paths. Decide which upgrades or replacements are compatible with the project, then verify that the audit reports no high or critical vulnerabilities and that the existing tooling still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript, vite
- Domain
- devops, security, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100