Get Yana Studio 1.5.

WHY THE WARNING APPEARS

Signed is different from notarized

Gatekeeper checks two things before letting an app run without asking: whether it's signed with a trusted Developer ID, and whether Apple has notarized that specific build (an automated malware scan). Yana Studio is signed (ad-hoc) but not notarized, so Gatekeeper shows a warning instead of blocking outright or opening silently.

METHOD 1 — RECOMMENDED

Right-click → Open

1. Open the .dmg and drag Yana Studio into Applications.
2. In Applications, right-click (or Control-click) Yana Studio and choose Open — don't just double-click it.
3. macOS shows a dialog saying it can't verify the developer. Click Open in that dialog.
4. The app launches. From now on, double-clicking it also works — macOS remembers this app.

METHOD 2 — IF ALREADY BLOCKED

System Settings → Privacy & Security

Use this if you already double-clicked and macOS refused to open it ("can't be opened because Apple cannot check it for malicious software" / "the developer cannot be verified").

1. Open System Settings → Privacy & Security.
2. Scroll to the Security section — you'll see a line saying "Yana Studio" was blocked because it isn't from an identified developer.
3. Click Open Anyway.
4. macOS may ask you to confirm once more (Touch ID or your password) — confirm.
5. Open Yana Studio again; it now launches normally.

WHAT NOT TO DO

Don't do this — it's unnecessary

Some guides suggest disabling Gatekeeper entirely (sudo spctl --master-disable) or stripping the quarantine flag from Terminal (xattr -cr). Don't do either. They turn off a real macOS protection for every app on your Mac, not just this one — and aren't needed; Method 1 or Method 2 above is enough, and only ever applies to this one app.

WHAT "AD-HOC SIGNED" MEANS

Signed, but with no Developer ID yet

"Ad-hoc signed" means the app's code is cryptographically sealed (so macOS can detect if the file was corrupted or tampered with after this build) using a signature not tied to any registered developer identity — different from being unsigned, but carrying none of the trust an Apple Developer ID certificate provides. It's a real, Apple-documented signing mechanism (codesign --sign -), used here only so the app can launch at all on Apple Silicon, not to imply any Apple review or endorsement.

WINDOWS

SmartScreen shows a similar warning

The Windows installer (.exe) is currently unsigned — the project doesn't have a paid Microsoft code-signing certificate yet. The first time you run the .exe, Windows SmartScreen will show "Windows protected your PC." Click More info → Run anyway to continue. This is the standard warning for an unsigned app, not a sign the app is broken or unsafe.

LINUX

AppImage needs the execute bit set first

For .AppImage: make it executable and run it directly — chmod +x Yana-Studio-*.AppImage && ./Yana-Studio-*.AppImage. For .deb: install with sudo dpkg -i Yana-Studio-*.deb, or open it with your distro's package manager. Linux doesn't have a notarization/SmartScreen-style warning layer like macOS/Windows, but the same principle applies: only download from the official Release page, and always verify the checksum.

VERIFYING YOUR DOWNLOAD

Check the checksum

Every release publishes a SHA-256 checksum for its installer files. To confirm your download wasn't corrupted or tampered with in transit, run in Terminal:

...and compare it against the checksum published on the release page. This is a data-integrity check, not a substitute for code signing/notarization — it confirms the file matches what was published, not that Apple/Microsoft reviewed it.