Component · for humans & their agents
App & Game Store Listing Validator
verified · first-partyactively maintained$0 during beta (was $39)
Store fields truncate rather than reject, and a localised listing blows limits the English one passed — so a Japanese page silently truncates while English looks fine.
by voxpop · Code Recycle maintainer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 117 tests · 9/9 mutations caught
Validates store listing copy against the published limits of Steam, the App Store and Google Play.
Validates store listing copy against the published limits of Steam, the App Store and Google Play.
THE SILENT FAILURE. Store fields truncate rather than rejecting. A short description cut mid-sentence is what a shopper reads. The limits differ per store and per field, are counted inconsistently for non-Latin text, and — the part nobody checks — a LOCALISED listing blows limits that the English one passed. The Japanese or German page silently truncates while English looks perfect.
MULTI-LOCALE VALIDATION IS THE POINT: it validates a set of localised strings and reports which locales fail which fields. A validator that only checks English reproduces the bug.
Apple's keywords field is a comma-separated TOTAL budget rather than per keyword, and is handled the way the platform does, naming which keywords were dropped. Counting never uses naive .length on text containing astral characters, and the unit used per field is documented.
Every limit is cited to a primary source. Where a limit could not be confirmed it is marked UNVERIFIED in the code rather than guessed.
VERIFIED: 117 tests, 9/9 mutations caught. Every mutation was observed FAILING before the source was restored — a test never seen to fail is a decoration.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function validateAppStoreListing( locales: Record<string, AppleLocaleFields> ): AppStoreListingReport;
export function validateGooglePlayListing( locales: Record<string, GooglePlayLocaleFields> ): GooglePlayListingReport;
export function appleKeywordsBudget( keywords: string[], budgetBytes: number = APPLE_KEYWORDS_BUDGET_BYTES ): KeywordsBudgetResult;
export function validateSteamTags(tags: string[]): SteamTagsReport;
export function validateSteamListing( locales: Record<string, SteamLocaleFields>, tags: string[] = [] ): SteamListingReport;
export function codepointLength(value: string): number;
export function utf8ByteLength(value: string): number;
export function truncateToUtf8Budget( value: string, budgetBytes: number ):;
export function validateTextField( store: StoreId, locale: string, field: string, value: string, limit: TextFieldLimit ): FieldReport;
export function validateLocalizedTextFields( store: StoreId, locales: Record<string, Record<string, string | undefined>>, limitTable: Record<string, TextFieldLimit> ): FieldReport[];
export function failingLocales(reports: FieldReport[]): FailingLocale[]; export type StoreId = "steam" | "appStore" | "googlePlay";
export type CountingUnit = "codepoints" | "utf8Bytes";
export type FieldLimit = TextFieldLimit | ListCountLimit;
export type FieldStatus = "ok" | "violation" | "unverified";01Capabilities
Does
- + Creator operations
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 117/117 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 23 source file(s) plus listing text
- capability contract All 3 observed capability reference(s) match the declared manifest (3 declared as cited source(s), not contacted)
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 4, 2026 | First public release. |