Type your site. That's the setup.
Liably opens it the way a visitor's browser does, before and after a cookie choice, and reads what it shows, loads and stores.
It only reads. Nothing on your site is changed.
Liably has 226 legal and 217 security checks for your website, app and code, built on 1,054 laws. Every issue comes with proof and a fix your AI can apply.
Or check your code in Claude Code, Cursor, VS Code and GitHub ActionsExample: Liably takes a site apart into what visitors see, what it loads, what it stores and what it runs on, and marks five issues: a button with no name, tracking before consent, a cookie set before a choice, a secret key in the code and a database table open to anyone.
Four numbers from people who measure this for a living. None of them are ours.
45%
of AI coding tasks came back with a security flaw.
Veracode · July 2025
28.65M
new secrets, such as API keys, were pushed to public GitHub in 2025.
GitGuardian · March 2026
95.9%
of the top million home pages fail accessibility checks a machine can run.
WebAIM · February 2026
about 50%
of 20,000 popular sites sent a cookie to a tracker before a consent choice there.
Rasaii et al. · PETS 2025
yoursite.comExample
125laws reach you
Where are your customers?
Counts describe Liably's research records as of 12 November 2026. Depth differs by country, and your report says how deep.
Open databases, keys left in the code, logins with no limit. Liably looks where attackers look, and it only looks.
Liably opens it the way a visitor's browser does, before and after a cookie choice, and reads what it shows, loads and stores.
It only reads. Nothing on your site is changed.
Every issue shows what was recorded, when, and the laws it touches. No grade, and nothing you have to take on trust.
Each issue carries a prompt for your coding agent. Paste it, approve the change, and Liably checks again.
Fixed means the next check no longer finds it.
Fix promptExample
Liably finding (High): Analytics loads before a consent choice. Seen: GET https://measure.example/collect on /, before any choice. Fix: load the analytics script only after the visitor accepts measurement cookies. Keep the change small, show me the diff first, and do not touch other files.
Liably runs inside your coding agent, your terminal and your CI. The check is the same one everywhere.
npx -y --package=@liably/cli liably setupAdds Liably to Claude Code, Cursor, VS Code and Codex. Code checks are part of the Liably plan and run on your machine or CI runner. Your source code stays on your machine unless you choose to send files. How to connect your coding agent
Example: your coding agent adds a newsletter form, checks its own change with Liably, finds a pre-ticked consent box and a route with no rate limit, and fixes both. The same check runs in the terminal, on the pull request and against the live site.
When a new law touches your project, Liably checks again and says what to do.
97 laws on file started in 2026 and 25 more already have a start date, fifteen of them on 1 January 2027. Example update: Colorado SB 26-189 starts on 1 January 2027; Liably checks the site again, finds two new issues and sends them with their fix prompts by email, webhook or to your coding agent.
Free check
€0
Liably
Each site or repository is its own project at the same price. Renews until you cancel. You can cancel online without signing in.
Short answers. The long ones are in the terms and the privacy notice.
No one can. Liably shows you what it finds, with proof and a fix, and tells you when the rules change. What you do with it is up to you.
No. Liably reports what it observes and names the laws it touches. It is not a law firm, and a finding is not a legal verdict.
No. The hosted check only reads what any visitor's browser receives. It sends no attack payloads and changes nothing.
Not by default. Code checks run in the Liably engine on your computer or CI runner. A summary without source code is synced only if you turn that on. Files you choose to send, from your coding agent or the dashboard, are stored encrypted.
Liably has rules on file for 128 countries and 74 states and regions, such as California and Ontario. Depth differs, and every report says how deep the coverage is for each market.
A full check of your site. Your three most serious legal issues are shown in full, and security appears as a count per area. No account needed.