PAGES
← all tools
◆ Digital Forensics & Incident Response

macos-unifiedlogs

v0.7.0 open-source

Free plan: not checked yet · Open source: yes

macos-unifiedlogs is a Rust library that parses macOS Unified Log files, extracting fields such as process ID, timestamp, log message, and subsystem.

What you can do now

Checking Plays…

Summary

macos-unifiedlogs is an open-source Rust library that parses Apple Unified Log files, aimed at DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. practitioners investigating macOS and other Apple-system evidence. You import it into Rust code or run its example iterator against a logarchive or live macOS system, producing JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. or CSV with bookmark/resume support. Its zero-copy entries, lazy message formatting, and bounded string cache suit analysts processing large collections without loading everything into memory. It sits in the macOS artifact-parsing category rather than as a standalone investigation platform. The project has 13 releases in the tracked window, with the last 42 days ago.

macos-unifiedlogs is a Rust library that parses macOS Unified Log files, extracting fields such as process ID, timestamp, log message, and subsystem.

How macos-unifiedlogs helps

What identifying metadata is associated with a log entry?

extracts Process ID, Thread ID, Activity ID, Parent Activity ID, Library UUID, Process UUID, Boot UUID, Timezone, and more

What specific details are included in the log message content?

provides both a Raw message from the UUID file and Message entries from the tracev3 file, which combine to form the Log Message

What technical information is available within the log data?

can extract Event Type, Log Type, Library, Subsystem, Category, and details from mach kernel error codes

What system events can be analyzed from the logs?

can analyze diagnostics data found in the diagnostics directory, including specialized information from HighVolume, Persist, Signpost, and Special subdirectories

Are there methods to process and view the gathered logs?

an available example binary can parse a logarchive into a JSOL or CSV file, or it can parse logs from a live system

What specific object information can be extracted from log entries?

supports parsing DNS info objects and Network Interface (NWI) objects from Unified Log entries

all 24 features, with the evidence for each →

Languages

Not documented

Features

24 capabilities

Built from macos-unifiedlogs's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What macos-unifiedlogs offers you

  • Built-in AI assistant5
  • Command-line interface4
  • Ticketing integration2
  • Administrative audit log1
  • Autonomous investigation and remediation1
  • CI/CD pipeline integration1
  • Extension marketplace1
  • MCP server1
  • Natural-language query1

All capabilities 24 capabilities
Copilot cloud agent Assigns tasks to Copilot or third-party agents such as Claude by Anthropic and OpenAI Codex to plan, research, and write code autonomously in the background and return a pull request. 24 other sources

Also counts toward: Built-in AI assistant, Ticketing integration

Apple Unified Logging format parsing Parses and interprets Apple Unified Logging and Activity Tracing formats, including tracev3 and uuidtext file types. 16 releases · 4 other sources · first seen Mar 2025
GitHub Copilot App (desktop workspace) Provides a native desktop workspace to start work on GitHub, track progress across multiple agents, review changes, and merge completed work. 20 other sources
AI-assisted pull request code review Provides automated pull request reviews on GitHub, with the ability to suggest edits and fix issues directly from the editor or a PR. 17 other sources
GitHub Actions CI/CD Automates build, test, and deployment workflows with real-time run visibility, a built-in encrypted secret store, and shareable links to specific log lines. 16 other sources

Also counts toward: CI/CD pipeline integration, Extension marketplace

AI-assisted code completion Provides inline code completions and next-edit suggestions inside supported editors and IDEs across all plans. 15 other sources

Also counts toward: Command-line interface

MCP server integration Connects Copilot to Model Context Protocol servers — including the built-in GitHub MCP Server and community-registered custom servers — to extend its context and capabilities. 14 other sources

Also counts toward: MCP server

Enterprise governance and audit controls Gives administrators enterprise-level controls over agent usage, AI credit spending, and audit logs across an organisation. 13 other sources

Also counts toward: Administrative audit log

Codespaces Offers cloud-hosted development environments that let developers start coding instantly without local setup. 12 other sources
GitHub Issues and project tracking Tracks work items and planning context that can be handed off directly to Copilot or third-party agents from Issues, IDE integrations, or messaging tools. 12 other sources

Also counts toward: Command-line interface, Built-in AI assistant, Ticketing integration

Multi-LLM model selection Lets users choose from multiple large language models optimised for different trade-offs such as speed, accuracy, or cost. 12 other sources
Agent mode Lets Copilot autonomously analyze a codebase, propose and make edits across multiple files, run tests, and validate results inside supported IDEs. 11 other sources

Also counts toward: Autonomous investigation and remediation, Built-in AI assistant

Copilot CLI Brings Copilot assistance to the command line, allowing users to get suggestions, run plans, and delegate tasks without leaving the terminal. 10 other sources

Also counts toward: Command-line interface

Custom instructions and agents Allows teams to define project-specific instructions via AGENTS.md and build or integrate custom agents to align Copilot with their coding practices. 10 other sources

Also counts toward: Command-line interface

Copilot Spaces (knowledge base) Creates a shared knowledge source from project documents and repositories so Copilot can answer questions with project-specific context. 7 other sources
GitHub Discussions Provides a dedicated community space for questions, answers, and open-ended conversations with customisable categories. 6 other sources
Pull requests Supports collaborative code review workflows with the ability to break large changes into dependency-ordered chunks and protect the main branch. 6 other sources
Copilot Autofix Automatically detects vulnerabilities and generates intelligent fix suggestions to eliminate security issues before code is merged. 4 other sources

Also counts toward: Built-in AI assistant

App modernization for Java and .NET Assists with upgrading and modernising existing Java and .NET applications as a Copilot-powered capability available on paid plans. 3 other sources
Copilot Chat Offers an AI chat interface within editors, github.com, and GitHub Mobile for asking questions, explaining code, and getting suggestions. 3 other sources

Also counts toward: Built-in AI assistant, Natural-language query

Code search and code view Enables fast, precise search across repositories with an integrated code browsing experience. 2 other sources
GitHub Desktop A native desktop application that simplifies Git workflows with visual diff views, commit history editing, and branch management tools. 2 other sources
GitHub Packages Hosts software packages publicly or privately so they can be published, shared, or consumed as dependencies within projects. 1 other source
GitHub Sponsors Enables financial support for open-source maintainers directly through GitHub. 1 other source

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for macos-unifiedlogs, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail macos-unifiedlogs puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Documentation timing

See whether macos-unifiedlogs's docs change before or after its release notes, release by release.

Documentation timing is included with Practitioner, Researcher and Business. When the docs come first, you can read about a change before it's announced.

See plans → Already subscribed? Sign in →

Coverage

Missing something? Tell us

What macos-unifiedlogs connects to, runs on and detects, read from its release notes and docs. So far: 3 new supported platforms.

Show

3 changes, tracked since Sep 14, 2026.

  • Oct 82026

    new macOS version coverage documentation

    Adds macOS 10.12 (Sierra), macOS 10.13 (High Sierra), macOS 10.14 (Mojave), macOS 10.15 (Catalina), macOS 11 (Big Sur), macOS 12 (Monterey). 7 in all.

    Source ↗

  • Sep 292026

    new macOS Ventura (13) format documentation

    With macOS 13 (Ventura)

    Source ↗

  • Sep 142026

    new GoldenGate and iOS 27 Unified Log support

    Initial support for GoldenGate and iOS 27

    v0.7.0 Source ↗

Changes per month New Updated Retired
2026-092
2026-101
How we count

Read from 3 of 6 release notes and docs updates we hold for macos-unifiedlogs. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through macos-unifiedlogs's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

6 entries

  1. October 20261
  2. September 20262
  3. May 20261
  4. June 20251
  5. March 20251
    Show
    Coverage in all entries

    6 entries

    Project health

    Issue, contributor and maintainer activity in mandiant/macos-unifiedlogs, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 65% of issues opened, last 12 months
    5. Median time to close 19 days first maintainer reply 32 hours
    6. Open backlog 13 of 58 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 13
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • features 5%
    • questions 5%
    • other 90%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.