Open-Source Software

Last updated: August 5, 2026

Fibich includes open-source components created and maintained by other people and organizations. Each component remains subject to its own license. Those licenses do not ask Fibich users to pay fees or royalties.

The inventory and downloads below match the dependency revisions currently resolved for Fibich 1.0.1. Nothing in Fibich’s own license limits the rights granted by the open-source licenses.

Read or download the complete ThirdPartyNotices.txt

Full copyright notices and license texts, 407,855 bytes. SHA-256:

4d0f937db6b7dc933cd9e8aad65bd20b0f9a7b81cf4f081431d4bc7d520f6311

Resolved component inventory

This is a concise index. The complete notices file above is authoritative for copyright statements, acknowledgments, and license text.

Component Resolved version License
AVFAudioExtensions0.5.1MIT
CDUMB2.0.3DUMB permissive license and bundled notices
CSpeex1.2.1BSD-3-Clause
CXXAudioRingBuffer0.1.1MIT
CXXDispatchSemaphore0.4.1MIT
CXXMonkeysAudio12.13.0BSD-3-Clause
CXXRingBuffer0.6.1MIT
CXXTagLib2.3.0Mozilla Public License 1.1; bundled utfcpp is Boost 1.0
CXXUnfairLock0.3.1MIT
FLAC binary XCFramework package0.2.0BSD-3-Clause
LAME binary XCFramework package0.1.2GNU Library General Public License 2 or later
Musepack binary XCFramework package0.1.2BSD-3-Clause and LGPL-2.1-or-later
mpg123 binary XCFramework package0.3.1LGPL-2.1
Ogg binary XCFramework package0.1.3BSD-3-Clause
Opus binary XCFramework package0.3.0BSD-3-Clause
SFBAudioEngine0.13.0MIT and bundled third-party notices
libsndfile binary XCFramework package0.1.2LGPL-2.1-or-later
Sparkle2.9.4MIT-style license and bundled third-party notices
Swift Collections1.6.0Apache-2.0 with Swift Runtime Library Exception
SwiftTagLib c2dc5436a4c82502d667dab57bb474a6743116ce Mozilla Public License 2.0
TTA binary XCFramework package0.1.2LGPL-3.0
Vorbis binary XCFramework package0.1.2BSD-3-Clause
WavPack binary XCFramework package0.2.0BSD-3-Clause

Source code and replacement materials

These are stable, version-specific downloads. They preserve the exact source revisions instead of relying on a moving upstream branch. The source contents and SHA-256 manifest document their provenance and integrity.

LGPL corresponding source and XCFramework build materials

LAME 0.1.2, Musepack 0.1.2, mpg123 0.3.1, libsndfile 0.1.2, and TTA 0.1.2. Includes exact component sources, package manifests, Xcode projects, Makefiles, configuration, patches, the shared build script, and libsndfile’s Ogg, FLAC, Opus, and Vorbis build dependencies.

SHA-256: fffe8ee42e5a29559e5f823505b977fdfb00de2ce17de5cb2b96789aee6a4fee

SwiftTagLib MPL-2.0 source

Exact revision c2dc5436a4c82502d667dab57bb474a6743116ce.

SHA-256: 85e5512688241dabe3e61aeb2a8745ee8eeecbeea6d8eb7e1df374045f524f9b

CXXTagLib MPL-1.1 source

Version 2.3.0, exact revision b570acead5e27006cb41ab5ff7443c8797b3b8e5.

SHA-256: 05a9815efb2774ba40d4520c7261313e8c5b2b0c2dcdfac735a2d984052b8aa8

Modified-library replacement status

Fibich links the five LGPL components as separate bundled dynamic frameworks: lame.framework, mpc.framework, mpg123.framework, sndfile.framework, and tta-cpp.framework. They are not statically linked into Fibich’s main executable, so this page does not offer proprietary application object files.

However, Fibich’s hardened app bundle and its nested frameworks are code signed. Replacing a framework changes sealed bundle contents. A compatible user-modified framework has not yet been rebuilt, substituted, signed, and launch-tested with the distributed app. This page therefore does not claim that modified-library replacement is currently usable.

Before Fibich is publicly distributed, the release process must:

  1. build a compatible modified universal macOS framework from the materials above;
  2. replace the matching framework in a copy of the release app and document the exact signing steps;
  3. verify that the modified app launches and exercises the replaced library; and
  4. publish the validated installation information required for the LGPL-3.0 TTA framework.

If that validation fails, the app’s packaging or signing configuration must change before release. Website wording alone cannot complete this requirement.