BuildNot yet confirmed elsewhere1 publisher3 min readPublished
macOS drops off The Open Group's UNIX register front page inside a four-day window
Apple's macOS entries dropped off The Open Group's UNIX register front page between 7 and 11 October, a dev.to post found by comparing Wayback captures. The UNIX 03 page still lists Tahoe, so the certificate's status is unclear and scripts should rely on tool behavior.
The Engineer · Build desk
What happened
- Wayback had held Tahoe entries for Apple silicon and Intel Macs on that URL since September 2025, and the 7 October capture still showed every Apple entry from Tahoe down to Monterey.
- The front page as fetched on 11 October lists IBM, Hewlett Packard Enterprise and The SCO Group, with no Apple entry.
- Both Tahoe certificates on the UNIX 03 page read "Registered on: 29-Aug-2025".
Why it matters
- contradiction Read the front page and Apple has no certified product. Read the UNIX 03 page and Tahoe is certified on Apple silicon and Intel, so the register disagrees with itself.
- exposure Commenters said government procurement checklists ask for "UNIX", and the post's author says the badge mattered to lawyers and purchasing departments. Those readers now have to check the product page, which stops at Tahoe.
- constraint The Open Group cannot be the route to a fix for sed -i or date flags, because the author notes that both toolchains are conformant.
- decision Teams sharing scripts between Macs and Linux CI have to test the commands on both. Neither answer from the register covers sed -i or date -v.
The Hacker News thread, posted on 10 October, had commenters calling the change a removal, a rendering bug and a non-story [20]. The post's author went to the HTML and read it narrowly. Tahoe is still certified, the front page no longer mentions Apple, and macOS 27 is not registered [22]. The same post offers three explanations: Apple files late, Apple stopped bothering, or somebody tidied the front page [22]. Hiding is a known pattern in that file. Sequoia and Ventura survive only inside HTML comments, and the author infers that old releases get hidden once a newer one is certified [21]. The captures bracket the change at four days and go no finer [3]. The author wrote: "Apple used to be on that front page and now isn't." [7]
macOS 27 shipped on 14 September [6]. By the 11 October fetch it had gone 27 days without an entry [17]. The post does not say how long Apple took to register earlier releases. For 27 days to point to a stopped practice, Apple would have had to register earlier releases within days of shipping.
The certificate was narrow even when it was current. UNIX 03 is version 3 of the Single UNIX Specification, last updated in 2004 [8]. Apple never certified against UNIX V7, and only AIX appears on that page [8]. OSNews worked from Apple's conformance documents for macOS 15.0. It reported that the test suites only pass on a Mac with System Integrity Protection turned off, the root account switched on, a case-sensitive APFS volume, and setuid uucp binaries placed in /usr/local/bin [18]. The post's author draws the conclusion: "So the certified system is a Mac nobody runs." [19]
Scripts break somewhere else. Linux CI runs GNU tools and Macs ship BSD-derived ones. Both claim POSIX, and POSIX says nothing about `sed -i` [9]. BSD sed requires an argument after -i, so Mac users write `sed -i '' 's/localhost/db/' conf.txt` [11]. On GNU sed 4.9 that line fails with "sed: can't read s/localhost/db/: No such file or directory" [12]. GNU takes the empty string as the script and the substitution as a filename, exits with status 2 and leaves the file alone [12]. Drop the empty string and Linux works, but BSD sed then takes the script as the backup suffix and the command breaks on the Mac [13]. The author ran the GNU side on Debian 13 with coreutils 9.7. The BSD behaviour comes from the macOS man pages [10].
Dates split the same way. GNU date takes -d and BSD date takes -v, and GNU answers `date -v+2d +%F` with "date: invalid option -- 'v'" [14]. `readlink -f` is mostly settled: macOS 12.3 added -f, and earlier releases returned "illegal option -- f", which now bites only teams that still run Big Sur machines [15].
What to watch
- A later Wayback capture or fresh fetch of /openbrand/register/ showing whether Apple returns to the front page.
- Whether macOS 27 gets a UNIX 03 entry on the product page, after 27 days without one at the 11 October fetch.
- Any statement from Apple or The Open Group on the change; the post cites none.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence58
- Adoption
- Insufficient
- Hype gap+5
- Incentives
- Insufficient
- Confidence60
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The main register page (/openbrand/register/), fetched on 11 October 2026, lists IBM, Hewlett Packard Enterprise and The SCO Group; Apple is not there.
- [2]
The Wayback Machine has had 'macOS version 26.0 Tahoe' for Apple silicon and Intel Macs on the register URL since September 2025, and the capture from 7 October 2026 still shows all the Apple entries, Tahoe down to Monterey.
- [3]
The capture from 11 October 2026 has none of the Apple entries, so Apple went missing sometime in the four days between the captures.
- [4]
The UNIX 03 product page still lists macOS version 26.0 Tahoe on both Apple silicon-based and Intel-based Mac computers.
- [5]
Both Tahoe certificates say 'Registered on: 29-Aug-2025'.
- [6]
The author found no entry for macOS 27, which shipped on 14 September.
- [7]
Apple used to be on that front page and now isn't.
- [8]
UNIX 03 means version 3 of the Single UNIX Specification, last updated in 2004; Apple never certified against UNIX V7, and on the V7 page only AIX shows up.
- [9]
CI usually runs on Linux with GNU tools while a Mac ships BSD-derived ones; both claim POSIX, and POSIX says nothing about sed -i.
- [10]
The author tested the GNU side on a Debian 13 box (GNU sed 4.9, coreutils 9.7); the BSD behaviour comes from the macOS man pages.
- [11]
On a Mac, BSD sed requires an argument after -i, so people write: sed -i '' 's/localhost/db/' conf.txt
- [12]
Run on GNU sed 4.9, the line sed -i '' 's/localhost/db/' conf.txt prints 'sed: can't read s/localhost/db/: No such file or directory'; GNU took '' as the script and the substitution as a filename, exited with status 2 and left the file alone.
- [13]
Dropping the '' works on Linux, but on macOS BSD sed takes the script as the backup suffix and the command breaks there instead.
- [14]
GNU date uses -d (date -u -d '2026-10-11 +2 days' +%F) and BSD date uses -v (date -v+2d +%F); on GNU the second form dies with "date: invalid option -- 'v'".
- [15]
Before macOS 12.3, readlink -f returned 'illegal option -- f'; Monterey 12.3 added -f, so the problem is mostly over unless a team still has Big Sur machines.
- [16]
None of these differences was ever going to be fixed by The Open Group, because both implementations are conformant.
- [17]
By the 11 October 2026 fetch, macOS 27 had gone 27 days since its 14 September ship date without a register entry.
- [18]
OSNews, going through Apple's conformance documents for macOS 15.0, reported that passing the UNIX 03 test suites means disabling System Integrity Protection, enabling the root account, formatting APFS as case-sensitive, and copying uucp binaries into /usr/local/bin with the setuid bit set.
- [19]
So the certified system is a Mac nobody runs.
- [20]
The Hacker News thread went up on 10 October, and commenters called the change a removal, a rendering bug and a non-story all at once.
- [21]
Sequoia and Ventura are still in the UNIX 03 page file, wrapped in HTML comments; the author infers old releases get hidden once a newer one is certified.
- [22]
The author's reading is that Tahoe is still certified, the register front page no longer mentions Apple, and macOS 27 has not been registered; explanations offered are that Apple files late, stopped bothering, or somebody tidied the front page.
- [23]
Commenters in the Hacker News thread pointed to government procurement checklists that ask for 'UNIX'; some also said The Open Group sued Apple over calling Mac OS X UNIX and that Apple found it cheaper to pass the tests and pay the license fee.
- [24]
The people who cared about the UNIX badge were lawyers and purchasing departments.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toIs macOS Still Unix? Apple Has Dropped Off the UNIX Register Front Page
1 article · October 11, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.