CoreTend

SUPPORT Diagnostics

Resolve issues without weakening macOS.

CoreTend 1.0.1 is Developer ID signed and notarized by Apple. It opens normally; the checks below confirm provenance.

Version 1.0.1macOS 14.0+arm64

01 / Path

Three checks before reporting a problem.

Every step keeps macOS protections enabled.

  1. Check the digest

    Compare the DMG's SHA-256 with the published SHA256SUMS beside it.

    Provenance

  2. Check the signature

    minisign -Vm SHA256SUMS -P … with the published key, and xcrun stapler validate on the DMG.

    Signature

  3. Install

    Open the .dmg, drag CoreTend to Applications, double-click it. No Gatekeeper exception is needed.

    Direct

02 / Details

A technical block ready to attach.

It contains no personal path or scan data.

CoreTend 1.0.1
CoreTend-1.0.1-arm64.dmg
minimum macOS: 14.0
architecture: arm64
Developer ID: yes (NSCUV5G738)
notarized: yes
SHA-256: 91026c89313e7b36a546b395ae4ba21dee2542e0e7592c22a0cec8cdb5d86fde
The app does not open after download

A notarized build opens normally. Check the SHA-256 and the Minisign signature published beside the file: together they confirm you have the distributed bytes. If it still will not start, open an issue with your macOS version — a signed, notarized build that does not launch is a bug, not a Gatekeeper block.

A scan cannot see some folders

Review exclusions and Full Disk Access. Grant only the permission required by the workflow you are using.

What should a report include?

The version, macOS release, architecture, affected module and reproducible steps. Remove personal file names from every screenshot.