Squossifrage

10.1 was released in 2014 and reached EOL in 2016. The screenshot appears to show a 10.1-p45 kernel that was built from December 2016 sources in September 2019, at a time when the latest release was 11.3. However, the Subversion revision number in the screenshot (r272678M) does not match any point on the stable/10 or releng/10.1 branches. To get that uname line, assuming neither the version string nor the screenshot have been manipulated, you'd have to have checked out the head (development) branch from Subversion, synced it to r272678¹ (11.0-CURRENT, October 2014), then replaced some or all of the tree (but not the Subversion metadata) with the tip of the releng/10.1 branch before building and installing a kernel in 2019.

¹ https://cgit.freebsd.org/src/commit/?id=e15d3f3c0978fad0ebbc...

Incorrect. They default to zsh for interactive use, but their /bin/sh is bash 2. They also ship a copy of dash, but it's not sufficiently POSIX-conforming to replace bash.

Three out of four aren't even companies. SUNET is the Swedish NREN, NetNod is a non-profit that manages Internet infrastructure services (like DNS and NTP) in Sweden, IIS is the non-profit that manages the Swedish TLDs.

The macOS userspace was never forked from FreeBSD or any other BSD. If anything, it was forked from NextSTEP. In actual practice, it is a collection of individual components taken from a variety of sources. When development of Mac OS X began in 1999, most command-line tools and a large part of libc were derived from either NetBSD or OpenBSD via NextSTEP. Over the years, there has been a shift toward FreeBSD. Apple maintain a collection of GitHub repositories of their Open Source components where you can see the evolution from one release to the next. Most of them have XML metadata indicating the origin of each individual component.

Info-Zip Unzip 6.00 was released in 2009 and has not been updated since. Most Linux distros (and Apple) just ship that 15-plus-year-old code with their own patches on top to fix bugs and improve compatibility with still-maintained but non-free (or less-free) competing implementations. Unfortunately, while the Info-Zip license is pretty liberal when it comes to redistribution and patching, it makes it hard to fork the project; furthermore, anyone who wanted to do so would face the difficult decision of either dropping or trying to continue to support dozens of legacy platforms. Therefore, nobody has stepped up to take charge and unify the many wildly disparate mini-forks.