Try the scanner
Free
Run scans and read public campaign intelligence.
- 25 scans / month
- 1 API key
- Public candidate feed
- Static evidence reports
Pricing
Static package evidence, candidate context, and a low-friction API gate before suspicious dependencies reach production builds.
Try the scanner
Run scans and read public campaign intelligence.
Your first paid step
Gate one project's dependencies in CI — the low-cost on-ramp.
For a single team
Gate suspicious updates in CI before they hit your build.
For 5–20 engineers
Standardise release checks across multiple repositories.
For larger orgs
High-volume gating with priority during load and an SLA.
Platform-team scale
Volume scans, SSO, SLA, and a procurement-friendly contract.
What is a scan? One package version evaluated, e.g. [email protected]. Re-scans within 24 h are cached and free. A typical 200-dep repo on every PR uses ~50–200 scans per month.
Compare plans
| Feature | Free | Starter | Pro | Team | Scale | Enterprise |
|---|---|---|---|---|---|---|
| Static package scans / month | 25 | 150 | 1,500 | 5,000 | 25,000 | Custom |
| API keys | 1 | 3 | 10 | 25 | 100 | Unlimited |
| CI gate endpoint | — | ✓ | ✓ | ✓ | ✓ | ✓ |
| Candidate campaign feed | Public only | Public only | Public + early alerts | Public + early alerts | Public + early alerts | Public + private alerts |
| Scan history retention | 30 days | 30 days | 90 days | 12 months | 12 months | Custom |
| Audit log | — | — | — | ✓ | ✓ | ✓ |
| SSO + SAML | — | — | — | — | — | ✓ |
| Uptime SLA | — | — | — | — | ✓ | ✓ |
| Support | Community | Community | Priority email | Priority email | Slack + named contact |
Questions
One package version evaluated, e.g. [email protected]. Re-scans of the same package@version within 24 hours are served from cache and don't count against your quota. A typical 200-dependency repo running on every PR uses 50 to 200 scans a month.
Every plan covers all nine ecosystems we support: npm, PyPI, RubyGems, Cargo, Maven, NuGet, Composer, Go, and Pub. The quota is shared across them. See /coverage for per-ecosystem corpus size.
Scans return a 429 with a retry-after window. The CI gate is configurable to fail open with a warning rather than block builds, so an exhausted quota never stops a deploy. You can upgrade in the dashboard without rotating API keys.
Yes. Plans are workspace-level — invite the rest of your team, share API keys, and the scan quota applies to the workspace. Team adds an audit log; Enterprise adds SSO/SAML and per-user identity.
Yes. Switch from monthly to annual in Stripe's billing portal for two months free on Pro and Team. Enterprise is annual-only with custom terms.
The cached path (the common case) returns in under 200 ms. First-time scans of a brand-new release land in 1–3 seconds depending on artifact size. The gate can be configured to fail open on timeout, so transient slowness never blocks a deploy.
No. The CLI computes the dependency list on your side; only the resulting package@version strings are sent to PkgRadar. We never read your repository, your lockfile contents, or any local code.
Yes, through Stripe's portal. Paid features stay active until the end of the current billing cycle. API keys keep working on the lower tier's monthly quota; we never silently disable them.