npm package reports / firecrawl

What ships in firecrawl?

firecrawl@4.54.0 ships a clean tarball: 103 files, nothing unexpected.

“JavaScript SDK for Firecrawl, the context API for AI agents: search, scrape, parse, crawl, map, and interact with the web, run Agent and Monitor jobs, and search scientific papers (PubMed, bioRxiv, me”

4.54.0version
103files
1.1 MBunpacked
0weekly dl

Findings

✓ No source maps, environment files, credentials, internal docs or other unexpected files in the published tarball.

Keep it this way: check every release in CI

This report covers one published version. ReleaseShield runs on every publish. It scans the exact tarball (npm pack), wheel or Docker image your pipeline builds and fails the release before anything unexpected reaches the registry.

# .github/workflows/release.yml
- uses: my2ctyw8h6-hash/release-shield@v1
  with:
    fail-on: high
  env:
    RELEASESHIELD_TOKEN: ${{ secrets.RELEASESHIELD_TOKEN }}

See plans: from $19/mo Re-scan firecrawl live

Maintainer? Show it in your README

The badge reflects the latest automated scan of the published tarball and refreshes on its own. ReleaseShield report for firecrawl

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/firecrawl.svg)](https://release-shield-app.vercel.app/npm/firecrawl?ref=badge)

Other package reports

chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks · @inquirer/select

Automated heuristic scan of the public tarball for firecrawl@4.54.0, run on 2026-11-17. Findings describe file contents and are not a judgment of the package's security or its maintainers; many are intentional. Maintainer and want this report removed or refreshed? Open an issue at github.com/my2ctyw8h6-hash/release-shield.