Find out before the reviewer does.
Peko reads your source, your binaries, your manifests, and the SDKs you did not write. Then it tells you what will get the build rejected, which file it is in, and what to change.
Fifty seconds, install to finding.
A recording of a real run on the example project. It installs in one line. The free lint reads every file and reports nothing. The audit reads the same code and returns twenty two findings, two of them blocking, each with the file, the line, and what to change.
A rejection costs you two weeks.
You submit on Thursday. On Monday you get a paragraph from review that names a guideline but not a file. The launch date moves.
How it works
Peko reads the lockfile, the manifests, the entitlements, and the privacy manifests inside the built artifact. Nothing is inferred. Most of store policy is prose, and a model reads the guideline against what the scan found.
A CLI and a GitHub check
Run it yourself before you push, or let the action run it on every pull request. Same engine, same report, same exit code.
Install
Download the binary for your machine from the latest release, check it against the checksum beside it, and put it on your path. Then run peko init and peko lint --all in your project. The lint runs on your machine, needs no account, and the rule database ships inside the binary. Builds for macOS on Apple silicon and Intel, Linux on x86_64 and arm64, and Windows.