PackageFix / CI/CD Guides / Node.js Dependency Security on Fly.io

Node.js Dependency Security on Fly.io Fly.io

Scan npm packages for CVEs before deploying to Fly.io. Keep your Node.js apps secure on edge deployments.

npm security on Fly.io

Add security scanning to your Dockerfile or fly.toml build.

# In your Dockerfile:
RUN npm audit --audit-level=high
RUN npm ci --only=production

# Or in .github/workflows/deploy.yml before fly deploy:
- run: npm audit --audit-level=critical
✓ Manual Scan

For a quick one-off scan before deployment, paste your package.json into PackageFix — no pipeline setup needed.

Scan your dependencies now — paste your manifest, get a fixed version back in seconds.

Open PackageFix →

No signup · No CLI · No GitHub connection · Runs 100% in your browser

Frequently Asked Questions

How do I add dependency scanning to Fly.io?
Add OSV Scanner or the ecosystem-specific audit tool to your Fly.io build configuration. The config snippet above works out of the box.
Does PackageFix integrate with CI/CD pipelines?
PackageFix is a browser tool for manual scans. For automated CI scanning, use OSV Scanner (Google) or pip-audit/npm audit in your pipeline. PackageFix generates the Renovate config and GitHub Actions workflow you can copy.
How do I fail a Fly.io build on critical CVEs?
Add --audit-level=critical to npm audit, or --fail-on=critical to pip-audit. The pipeline aborts if critical CVEs are found.
What is the OSV Scanner?
OSV Scanner is Google's open-source CLI tool that queries the same OSV database PackageFix uses. It's ideal for CI/CD integration.