You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] @mendable/firecrawl-js@4.42.4 still installs vulnerable axios@1.18.0 through an unused firecrawl@4.30.1 dependency #4927
Describe the Bug @mendable/firecrawl-js@4.42.4 pins axios@1.20.0 (thanks for #4875). It also depends on firecrawl@4.30.1, which pins axios@1.18.0, so every install of @mendable/firecrawl-js still includes a vulnerable axios. Dependabot and npm audit flag 12 axios advisories that are fixed in 1.20.0.
The firecrawl package is the same SDK published under another name. .github/workflows/publish-js-sdk.yml deletes this line before it publishes the firecrawl name (sed -i '/"firecrawl":/d' package.json). We compared the 4.42.4 tarballs: the dist/ files are identical, and "firecrawl" appears in the bundle only in the inlined keywords array. Nothing imports or requires it, so the dependency seems to have no runtime purpose. Your audit automation still bumps it, for example 4.16.0 → 4.30.1 in #4092.
Why does @mendable/firecrawl-js depend on firecrawl?
To Reproduce
Create an empty project: mkdir repro && cd repro && npm init -y
Run npm install @mendable/firecrawl-js@4.42.4
Run npm ls axios and npm audit
axios@1.18.0 is installed under firecrawl@4.30.1, and npm audit reports 3 high severity vulnerabilities (see Logs)
Expected Behavior
Installing @mendable/firecrawl-js@4.42.4 installs only axios@1.20.0. Either:
remove the firecrawl dependency from apps/js-sdk/firecrawl/package.json (preferred, if it is unused), or
bump it to firecrawl@4.42.4, which uses axios@1.20.0, and release a new @mendable/firecrawl-js.
Screenshots
N/A (see Logs)
Environment (please complete the following information):
Activity