macos-unifiedlogs
v0.7.0 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on macos-unifiedlogs's page any more, so we've brought you to the top.
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
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
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
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 →We check each docs page on a fixed schedule, so every gap is a range rather than one number. A release we can't place on either side is shown as "Can't tell".
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.
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.
-
Sep 292026
new macOS Ventura (13) format documentation
With macOS 13 (Ventura)
-
Sep 142026
new GoldenGate and iOS 27 Unified Log support
Initial support for GoldenGate and iOS 27
Databases & data platforms 1
Operating systems 8
Nothing first seen in this window. That doesn't mean macos-unifiedlogs shipped nothing, only that we found no record of it.
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
6 entries
No entries match these filters.
- October 20261
- September 20262
- May 20261
- June 20251
- March 20251
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.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 65% of issues opened, last 12 months
- Median time to close 19 days first maintainer reply 32 hours
- Open backlog 13 of 58 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 13
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- 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.