Scan your dependencies → plain-English legal, license & data-rights risk. In 60 seconds.
Each one is a latent liability — until a questionnaire, fundraise, or C&D makes it expensive.
Cache? Resell? Train on it? Compete?
Bans & lawsuits (Google v. SerpApi).
PII to an unvetted sub-processor. GDPR/CCPA.
AGPL copyleft in your private code.
Overage cliffs, auto-tier, lock-in.
Bot-circumvention = DMCA exposure.
Reads your manifests. Infers how each API is used.
Matches the fine print. Ranks by priority.
Plain-English. Sourced. Calm — not scary.
Points to review 1 address first · 2 look into soon · 1 plan ● Address first Bypassing bot protection (DMCA anti-circumvention) why: deps include curl_cffi, cloakbrowser — the theory in Google v. SerpApi do: use an official API / data license §1201 ● Look into soon Stripe — PII / sub-processor · ● Plan OpenAI — outputs can't train rivals
Not another security or cost scanner — those have giants. Vetly reads the contractual fine print everyone else skips: every clause that creates a legal, license, or data-rights obligation, ranked by priority.
| Capability | One-off prompt | Vetly |
|---|---|---|
| Knows how your code uses each API | — | ✓ |
| Tracks when terms change | — | ✓ |
| Portfolio across deps & clients | — | ✓ |
| Exact clause + precedent | partial | ✓ |
| Runs in CI / Claude Code | — | ✓ |
| Code stays on your machine | — | ✓ |
Newest scan per client, by priority. White-label brief in a click.
No — informational triage. It quotes the clause and says when to look closer; it never says "you're cleared."
No. Local & in-browser modes send only provider names + boolean flags. A public GitHub URL is fetched on our server; private code → use the CLI.
Yes — a CLI (exits non-zero on a critical) and an MCP server.