about

Built from the things that broke other people's apps.

Japheth Jerry

Japheth Jerry

Creator, Periderm CLI

Shipping with AI is fast. Launching to real users is brutal. Periderm CLI exists because the gap between “it works on my machine” and “it survives the real world” is where products lose users, money, and trust.

Why it exists

A while ago my feed filled up with a new kind of video: people showing, step by step, how to find legal gaps on small websites and turn them into demand letters and payouts. The targets weren't big companies. They were solo founders and small teams who shipped fast and never knew what they'd missed. That stuck with me, because most of those people would have fixed it in an afternoon if anyone had told them.

The legal videos weren't the only ones. Just as many showed developers the quiet ways apps lose users: errors that fail silently, screens that break the moment real data shows up. Most apps are only ever tested with perfect data, a full profile, a fast connection, a happy path, and nobody plans for the user with no avatar, the empty list or the request that times out. Those are the bugs people leave over without telling you.

So I started saving them. Every one of those videos, every clip of an app falling over on launch day, every post-mortem about a surprise cloud bill, every article about the thing you should always check and nobody does. Each one became a rule. That collection is where Periderm's checks come from, and it still grows every week.

Legal gaps are one part of it, not the point of it. Most of what Periderm catches is plainer and more common: keys in the browser, routes anyone can call, errors that vanish silently, loops that run up a bill overnight.

The problem

Linters catch syntax. Tests catch logic you thought to write. Neither catches the embarrassing stuff: missing fallbacks on avatars, silent form failures, dead legal links, unverified webhooks, or infinite loops behind a feature flag that only show up when real traffic hits.

AI coding assistants make you faster. They don't make you launch-ready. Someone still has to ask: would a senior engineer sign off on this?

The work

Periderm runs 150+ deterministic checks across your codebase: AST analysis, filesystem inspection, migration analysis, privacy-policy cross-referencing and SEO validation. They're rules, not a model's opinion, so the same code always gets the same answer. On paid plans, an AI reviewer adds a second read on top.

One command. Three scores. A verdict. The exact files to open.

The standard

We named it after the outer protective layer of a plant — the part that keeps the inside safe from the environment. That's what we want Periderm to be: a thin, reliable shell between your code and the chaos of production.

Not another dashboard you forget to check. A habit wired into your terminal — or your browser, if you'd rather not touch one.

Who we're for

The solo maker shipping their fifth side project with Cursor. The founder who just wired Stripe and needs to know the webhook handler is safe. The vibecoder who has never opened a terminal but still needs to know their app won't bankrupt them on launch day.

If you care about real users more than green CI badges, this is for you.

Where we're going

Today: scan from your terminal, your browser, your AI agent or every pull request with the GitHub Action. Org-wide policies, scan history with diffs, and new checks every week. Tomorrow: more of the things nobody tells you to check, until there's nothing left that only shows up after launch.