Observed by Atlas — nobody has proved they control this domain. Is it yours?
Peko
OBSERVEDChecks app store compliance before you submit
- FRESHNESS
- 0.83
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 22
- IN THE FLOW
Peko reads source code, binaries, manifests, and third-party SDKs in a mobile app build to find issues that would get it rejected by app store review. It runs mechanical lint checks for free, and offers paid audits where a model interprets policy prose against the code. It is aimed at mobile app teams using Flutter, React Native, MAUI, Unity, or native, who need to pass Apple and Google review and fill out privacy forms like Data Safety and App Privacy.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
Unlimited lint runs, in the CLI and the GitHub Action · 46 mechanical rules, compiled into the binary · Rejection diagnosis, unlimited · Flutter, React Native, MAUI, Unity, and native · Rule database updates
3 audit cycles a month · Each cycle is 7 days of audits against one app · 326 interpretive rules, read against your code · Privacy form answers · 3 seats
9 audit cycles a month · Each cycle is 7 days of audits against one app · A higher ceiling for one run, so a large codebase fits · 10 seats
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Peko yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Peko? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it