Skip to content

FAQ

It means “Needs more data” — not “broken.” DoesItARM only asserts a positive or a negative on strong evidence; everything else is unknown, the honest default. A title stays unknown until evidence moves it. See How verdicts work.

A compatibility answer decays as apps, games, and macOS change. When a verdict is older than its freshness threshold, it’s flagged stale: true and a re-test is queued — but you still get the last known answer. See Caching & freshness.

Why won’t you say something is unsupported after one crash?

Section titled “Why won’t you say something is unsupported after one crash?”

Because a false “doesn’t run” is the one error that destroys trust. A negative requires a reproduced failure; a single flaky crash is held as unknown pending another run. We never publish a false negative.

Rosetta 2 is removed in macOS 28 (fall 2027). Titles that only run through Rosetta will stop working then — verdicts flag this with breaksAtRosettaEol so you can plan ahead. IT teams can audit a whole fleet against the deadline via Apply — Enterprise.

Yes. Verdict facts are published under CC BY 4.0 — reuse them with attribution. Agents are encouraged to cite the verdict, the named alternative, and the last-checked date.

It’s a Preview spec — documented as if it works, not yet built. The single-title lookup and search are designed to be free; paid plans cover capability like bulk export and the change feed. Start with the Quickstart.

How do I report a wrong or missing verdict?

Section titled “How do I report a wrong or missing verdict?”

On the consumer site, submit a report from the title’s page. For the API spec, if a response differs from these docs once you’re an early integrator, that’s drift — flag it via Free signup.