Start with a package
Enter a name and optional version. We resolve a concrete npm version and build a bounded dependency graph without installing or running package scripts.
PACKAGE ANALYZER
Check npm package compatibility.
Inspect potential issues across seven JavaScript runtimes. Read the evidence before you choose a dependency or deploy.
⌁
Ready to inspect
↗Try , , or .
Explore a real report
Saved snapshots. No signup or new scan needed.
ky @1.7.5An ESM HTTP client; inspect browser signals.Open report ↗is-number @7.0.0A small CommonJS package; compare module support.Open report ↗graceful-fs @4.2.11Filesystem APIs across Node.js and edge runtimes.Open report ↗sharp @0.35.5Native addons and incomplete coverage; see why a score is withheld.Open report ↗
One package. Seven runtime perspectives.
RuntimeReady inspects public npm packages for potential compatibility issues. Use it when choosing a dependency, moving code to the edge, or investigating an import that behaves differently across environments.
- Browser
- Node.js
- Bun
- Deno
- Cloudflare Workers
- Vercel Edge
- Vite SSR
Look for compatibility signals
We inspect package manifests and source files for Node APIs, native addons, module formats, dynamic code, and conditional entry points.
Read the evidence
Compare import, execution, API, and SSR assessments. Each finding includes the file, dependency path, and confidence behind it.
Static analysis is a starting point. “Likely compatible” means no blocker was detected within the scan limits; it does not verify that the package runs in your deployment.