pkgscan.dev · Documentation
pkgscan.dev pricing and scan limits
Every scan returns the full findings from every engine, and every result is public whether or not you have an account. Paid plans add scan volume, API keys, and team features. Quotas reset on the UTC calendar month.
Updated 2026-11-05
Plans
| Plan | Price | Scans / month | API access | Notes |
|---|---|---|---|---|
| Free | $0 | 5 | — | Full findings, public results |
| Hunter | $19/mo | 100 | Included | For regular dependency checks |
| Operator | $99/mo | 500 | Included | For CI jobs and scripts |
| Team | $199/mo | 1,000 | Included | Team seats and shared usage |
| Enterprise | Custom | Custom | Included | SSO, custom volume, dedicated support |
API keys are available on every paid plan, up to five per account. A key uses your plan's scan allowance and stops working if the plan returns to free. Upgrades apply immediately; downgrades take effect at the end of the current billing period. Enterprise is sales-led — contact [email protected].
What counts as a scan
- Starting a scan from a file upload, a registry PURL, a skill PURL, or a hash lookup counts once against the monthly quota.
- Viewing an existing report, including someone else's public report, does not count.
- Multi-platform submissions (the same package on two registries) count as one scan when submitted together.
- The quota is checked and consumed server-side before the scan runs, so the limit cannot be bypassed by retrying.
Why there is a free tier
A public report is useful to everyone who is about to install the same package, so pkgscan keeps results readable without an account. The free allowance exists to keep scanning cheap enough to offer without turning it into an abuse vector for compute. If you need more volume, the paid plans are the same product with a larger allowance.
Related: privacy and data handling, API and MCP access.
Check a package or file now: scan it on pkgscan.dev.