Repository navigation
macOS Inspector 1.3.2
macOS Inspector 1.3.2
macOS Inspector 1.3.2 makes changes between Application Trust scans easier to understand and investigate.
What is new
- Application changes now explain whether the evidence is consistent with an expected update, a macOS update, changed executable contents, a new trust concern, a signing identity change, or a trust regression.
- Version, Team ID, signature, Gatekeeper, notarization, hardened runtime, signature type, executable hash, permissions, bundle path integrity, trust result, and severity are compared when relevant.
- High-priority trust regressions, signer replacements, bundle identity changes, and integrity problems appear before routine update context.
- A current failed, review, or unknown trust result cannot be hidden by a possible update label.
- Weakened executable or Info.plist permissions and executables that resolve outside their application bundle receive dedicated explanations and next steps.
- Applications that no longer appear in the current inventory are counted and shown as review items. The dashboard asks for confirmation instead of assuming that the application was removed or that its disappearance is malicious.
- The Application Review queue includes a Changed since last scan filter. The complete change set remains available even when the summary is limited to the highest-priority items.
- Standalone investigation summaries include the same change explanations and field comparisons.
How it works
Open a completed Application Trust scan that has an earlier scan with the same collection scope. The dashboard automatically selects the newest comparable scan and places the most important changes in What changed and how the evidence connects.
Use Changed since last scan to review every current application with changed evidence. Expand a change to compare the previous and current values, then follow the displayed validation step. Applications that are no longer present appear in the change summary because there is no current application card to open.
These labels prioritize investigation. A possible update label does not prove that an update is legitimate, and a changed or missing application is not proof of tampering.
Safety and privacy
This release does not add file uploads, automatic removal, quarantine, or background network requests. Comparison logic uses reports already stored in the local report directory.
Online OSINT remains opt-in. Process containment still requires an explicit confirmation in the local dashboard.
Install
- Download
macos-inspector-1.3.2-macos.zipandSHA256SUMSfrom this release. - Run
shasum -a 256 macos-inspector-1.3.2-macos.zipand compare the complete result withSHA256SUMS. - Extract the archive and double-click macOS Inspector.command.
The portable release is not Apple-signed or notarized. Verify the checksum before opening it. If macOS blocks the first launch, use Finder's Control-click, then Open. Do not disable Gatekeeper globally.
Artifact
Filename: macos-inspector-1.3.2-macos.zip
SHA-256: f7072237250b9be2f15cbe395469ee1033afd8f9c951e10e6a071d6a46f062e3
Known limitations
- A comparison depends on equivalent collection scope and the evidence available in both scans.
- Missing applications can reflect intentional removal, access differences, or inventory changes. Confirm the reason before drawing a security conclusion.
- A matching Team ID and version change support update context but do not authenticate the release by themselves.
- Signature, Gatekeeper, notarization, and filesystem observations describe the inspected state. They do not label an application as malware or safe.
- The portable release is not Apple-signed or notarized.
Read the README, Installation guide, Usage and interpretation guide, Threat model, and Changelog before using the tool in an investigation.