Skip to content

macOS Inspector 1.4.3

Choose a tag to compare

@bacescuandrei bacescuandrei released this 04 Oct 08:40
· 10 commits to main since this release

macOS Inspector 1.4.3

This release makes scan comparisons easier to interpret and adds a traceable follow-up after an explicit process action. Both dashboard views now show when evidence was collected, what was checked, and which differences the available evidence can actually support.

What changed

Recorded scan context and repeat checks

  • About this scan shows start and completion times, report age, selected sections, exact application target, tool version, and finding filter.
  • Run these checks again preserves the recorded sections and application target, uses current settings and case fields, and still asks before an online check. Unsupported scope and duplicate requests are blocked.
  • Changes since last comparable scan is visible in Simple and Analyst views. It shows the actual earlier scan ID and completion time, with View earlier scan, expandable highlights, and all comparison counts.
  • Baseline selection uses timezone-aware completion times and matching recorded hosts, collection sections, application targets, and report identities. A matching hostname is not device authentication.

More careful comparison and inventory handling

  • Unreadable application directories are recorded as discovery gaps while successfully discovered applications remain in the report. They no longer disappear silently from the inventory.
  • An unknown result or collection error cannot round completion up to 100%.
  • Filtered, incomplete, or missing collection evidence makes affected additions/disappearances Not comparable instead of zero. Differences between records actually present in both scans remain available.
  • Local IOC/YARA files and relevant nonsecret configuration receive before/after content fingerprints. Missing, incomplete, unstable, or changed fingerprints prevent unsupported finding-presence and numeric-index comparisons.
  • Manual comparisons use Baseline only, Comparison only, and Changed record, not resolved-incident wording. They preserve raw differences and show N/A for unsupported index deltas. Standalone comparison reports and investigation summaries include the same interpretation limits and snapshot times.
  • Security-control regressions remain visible even when an unrelated comparison section is incomplete.

Process action history and outcome rechecks

  • Process action history shows recent locally recorded signals in both views, with access to the preserved source report.
  • Recheck process outcome collects a new, unfiltered Live Triage snapshot linked to that action. It is read-only and sends no signal.
  • Follow-up distinguishes the same identity still observed, PID reuse, zombie state, the original PID not observed, and insufficient evidence. No result marks an investigation resolved automatically.
  • New action records and bounded process snapshots include numeric owner and start identity. Older logs remain visible, but missing identity data cannot establish an identity-aware outcome.

Validation and setup

  • Detection regression validation evaluates 18 bundled synthetic trust and response scenarios from the HTML page and downloads a JSON result. These fixture counts are not real-world malware detection accuracy.
  • Dashboard tests now run in Chromium and Playwright WebKit, with targeted automated accessibility checks, keyboard focus, narrow layouts, escaped evidence, linked follow-up, and download checks.
  • The double-click launcher tries compatible Python installations instead of stopping at an incompatible first candidate. If none is found, it opens offline setup help. No runtime, dependency, or software is installed automatically.
  • Reopening an existing dashboard no longer removes the first launcher's PID tracking file.

How to use the new workflow

  1. Open the dashboard with macOS Inspector.command and run Check this Mac.
  2. Read About this scan before interpreting its assessment or comparing it with an earlier report.
  3. Use View earlier scan to inspect the actual automatic baseline. Read any Not comparable reason before treating a missing application or finding as a change.
  4. Before containment, preserve relevant evidence and validate the process. Confirm Terminate or Force kill only when justified.
  5. In Process action history, select Recheck process outcome and open the linked later snapshot. A missing PID does not prove that related activity stopped or that a security concern was fixed.

Verification

Local verification passed 113 Python tests, 50 browser tests across Chromium and WebKit, and all 18 synthetic scenarios. Syntax, compilation, documentation links, deterministic rebuilds, extracted-package startup, Git integrity, and privacy checks also passed. GitHub CI repeats Linux/macOS tests on Python 3.10 and 3.13, both browser engines, and portable packaging before publication. The CI artifact is checked against the local package byte for byte.

Boundaries

Collectors remain read-only. Process response still requires explicit confirmation, a recent authorized snapshot, current-user ownership, and live identity revalidation. No reputation database, automatic remediation, telemetry, or evidence upload was added. Online intelligence remains opt-in.

The action log is private but not tamper-proof and retains only one previous file; the dashboard shows up to 50 recent actions. Rule capture is not an atomic filesystem snapshot. Playwright WebKit coverage is not a claim that every shipping Safari version or screen reader was tested. Synthetic fixtures are regression checks, not an independent detection benchmark.

The portable release still requires Python 3.10 or newer and is not Apple-signed or notarized. Protected evidence can remain unavailable without broader permissions; do not disable macOS protections just to make checks green.

Install and artifact

Download the ZIP and SHA256SUMS from this release, compare the full SHA-256 before extraction, then double-click the launcher. If Python is missing, open docs/START_HERE.html for setup instructions.

Filename: macos-inspector-1.4.3-macos.zip
SHA-256: d4fcff9aab678fd6d7687c300a3c0c501db6ee4fc149c23a8f349ccc69eebf21

See the README, Usage guide, Validation guide, and Changelog for complete instructions and changes.