Get started

Everything happens in your terminal. Open one, paste the command this page gives you, and it walks you through the whole thing: installing, checking two sample apps, and auditing the one that passes every check. It runs there, not in this page, and this page moves on when it finishes.

What it does, in order

Installs one file after checking it against the checksum published beside it. Fetches two small iOS apps into ./peko-demo and touches nothing else. Checks the first, which has planted problems, and finds them. Checks the second, which is written carefully, and finds nothing. Then audits that second one, which reads the code rather than the files, and finds twenty things no file states.

The audit is free

It runs against our own sample app, whose answers are already worked out, so it costs nothing however many people try it. Pointing it at your own code is what a plan buys.

Or let your coding agent do it

Claude Code installs it as a plugin with two commands: /plugin marketplace add official-peko/peko, then /plugin install peko@peko. The first one only registers where the plugin comes from, so both are needed. Cursor and anything else that reads a prompt can be pointed at peko.so/skill.md, which carries the same instructions and stays current without reinstalling.

Run it on your project

Run peko init and then peko lint --all. Every finding names the rule, the file, and the line, and says what to change. The lint reads your files on your machine and sends none of them.

Run it on every pull request

The GitHub Action runs the same engine on a pull request, and findings land on the line they belong to through Code Scanning. Pin the version.

Make an account, when you want more

Everything above is free and stays free. An account adds rejection diagnosis and the audit tier, which reads the code with a model and judges the guidelines a file cannot settle on its own.