Lite is free. Pro adds this and the rest of the quality layer.
An online storethat takes payment.
A store is where a pasted key or a broken checkout button costs real money. Adams guards the parts that hurt most.
Lite and Pro
// the problem
What goes wrong
The riskiest file is the one that chargesCheckout code touches your payment key. An AI wiring it up may paste the key where the code can see it, and a public repository then exposes it.
Most buyers are on a phoneA product grid that looks fine on a laptop can push the buy button off the screen at 375 pixels. Nobody tells you, they just leave.
// what adams does
What Adams does
Guards the payment keyLite: a key written into a file is caught before the commit, and moved to an env file that git ignores.
Checks the checkout at three widthsPro: product, cart and checkout pages are opened at phone, tablet and desktop widths and any overflow is named.
Puts the biggest risk firstPro: say hey adams and it reads the project, then offers the safest next step first, such as moving a key before testing a payment.
// worked example
An example
Hey adams on a test store
A real run on a test store project, kept as it printed.
~/project~/your-project · example
hey adams
my-store · Next.js + Stripe · no plan yet · 1 open risk
A key looks pasted into app/api/checkout/route.ts, so anyone who sees the code can use it
1. Move the key out of code (recommended)
2. Check if it went public
3. Replace the old key
4. Test a payment
// faq
Questions
Does Adams touch my payment provider?
No. It reads your project files on your machine. It has no connection to Stripe, Shopify or any payment account.
Can it prove my checkout is secure?
No. It catches common mistakes such as pasted keys. Test payments in your provider test mode before you go live.
Which part is free?
The secret, git and leak guards. Hey Adams and the page checks are Pro.
// related