Verify it yourself

DisplayPilot is a new paid app with no reviews yet, so please do not take our word for anything. Every claim on this page can be checked on your own Mac with the commands below. The outputs quoted here are verbatim from the shipped 5.0.2 build.

1. Is it really ours, and did Apple notarize it?

codesign -dv --verbose=2 /Applications/DisplayPilot.app
  Authority=Developer ID Application: yanming hua (7P2P353LBW)
  Format=app bundle with Mach-O universal (x86_64 arm64)
  flags=0x10000(runtime)

spctl -a -vv -t exec /Applications/DisplayPilot.app
  accepted
  source=Notarized Developer ID

xcrun stapler validate /Applications/DisplayPilot.app
  The validate action worked!

The binary is signed with our Developer ID, Apple scanned and notarized it, and the notarization ticket is stapled to the app so it validates offline. A modified copy fails all three checks.

2. Did the download arrive intact?

shasum -a 256 ~/Downloads/DisplayPilot-5.0.2.dmg
  d88cc144cb25b57dce109a7ac4f2dd93b33856268449bc49b07d26c9ccd73bdf

The same value is published in the Homebrew cask, so there are two independent places to compare against:

brew cat huayanming/tap/displaypilot | grep sha256

If your value differs, do not run the file.

3. Does it phone home?

The app's own code contains exactly one endpoint: /api/redeem on our licence service. It is called only when you paste a short code — the long DP- code is verified entirely offline and never touches the network. Update checks are off by default (SUEnableAutomaticChecks and SUAllowsAutomaticUpdates are both false); if you switch them on, they fetch appcast.xml from our site and nothing else.

Watch it yourself — open the app, leave it idle, then:

lsof -i -P | grep -i displaypilot

With update checks off it prints nothing. The app never sends usage data, crash reports or an identifier to us; there is no analytics code in it.

4. Does activation really work without a network?

Turn off Wi-Fi, paste a long DP- code into the licence field, and it activates. The key is embedded in the app: an Ed25519 public key verifies the code locally, and the code is not bound to a device.

5. What you cannot check this way

• Whether the cleanup logic is correct. It touches only 13 kinds of rebuildable artifacts and quarantines for 30 days first. We publish the reasoning and the checks in the audit report rather than asking you to trust the UI.
• Whether the display work is right for your panel. That is what the 14-day trial is for.
• Whether we are pleasant to deal with. No page can prove that. Email us and see.

If any command above does not produce the output shown, that is a bug in our documentation or in our build — tell us at Support and we will fix it, publicly.

How we audit this product (and what we got wrong)

The scrolling numbers on the front page

The front page quotes a measured improvement in scroll response. That measurement comes from the app's own offline benchmark, which you can run yourself — it drives the interpolator frame by frame with a fixed timestep, without intercepting any real input, and prints the response shape:

DisplayPilot --scroll-selftest

On our test panel (120 Hz) the first frame went from 3 to 9 points and time-to-90% from 158 ms to 133 ms. Those numbers describe the algorithm's response, not your hardware, so expect your own run to differ.