Skip to content

docs(compliance): the klib notice stance (#1166) #1245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michalharakal merged 1 commit into from
Sep 1, 2026
Merged

docs(compliance): the klib notice stance (#1166) #1245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions ...ends/skainet-backend-jni-cpu/src/main/resources/META-INF/THIRD-PARTY-NOTICES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,21 @@ The I2_S GGUF wire-format handling in `skainet-io-gguf` was written against the
sources of [BitNet.cpp](https://github.com/microsoft/BitNet) (MIT, © Microsoft
Corporation) — a reimplementation of the layout rules, not copied code. See the
interpretation notes in `sk.ainet.io.gguf.I2sRepack`.

## Kotlin/Native klibs — how this notice reaches them

Kotlin/Native klibs have no `META-INF` resource mechanism, so this file cannot
physically travel inside the klib the way it travels inside the JVM jar and the
Android AAR. The stance for klib consumers, decided in
[#1166](https://github.com/SKaiNET-developers/SKaiNET/issues/1166):

- The klibs of a release embed the same static archive compiled from the same
sources as the jar in **the same Maven artifact family and version** — this
notice, shipped in that release's jar, is the authoritative notice for every
artifact of the release, klibs included.
- The source of truth is versioned in the repository: `LICENSES/MIT.txt`, the
`.license` sidecar next to the vendored file, and
`native/src/vendor/neogpu/README.md`.
- An application that links a SKaiNET klib into a shipped binary should carry
the NeoGPU MIT notice in its own third-party attributions (as it should for
any statically linked MIT code); the license text above is the text to carry.
18 changes: 18 additions & 0 deletions ...kainet-backend-native-cpu/src/jvmMain/resources/META-INF/THIRD-PARTY-NOTICES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,3 +52,21 @@ The I2_S GGUF wire-format handling in `skainet-io-gguf` was written against the
sources of [BitNet.cpp](https://github.com/microsoft/BitNet) (MIT, © Microsoft
Corporation) — a reimplementation of the layout rules, not copied code. See the
interpretation notes in `sk.ainet.io.gguf.I2sRepack`.

## Kotlin/Native klibs — how this notice reaches them

Kotlin/Native klibs have no `META-INF` resource mechanism, so this file cannot
physically travel inside the klib the way it travels inside the JVM jar and the
Android AAR. The stance for klib consumers, decided in
[#1166](https://github.com/SKaiNET-developers/SKaiNET/issues/1166):

- The klibs of a release embed the same static archive compiled from the same
sources as the jar in **the same Maven artifact family and version** — this
notice, shipped in that release's jar, is the authoritative notice for every
artifact of the release, klibs included.
- The source of truth is versioned in the repository: `LICENSES/MIT.txt`, the
`.license` sidecar next to the vendored file, and
`native/src/vendor/neogpu/README.md`.
- An application that links a SKaiNET klib into a shipped binary should carry
the NeoGPU MIT notice in its own third-party attributions (as it should for
any statically linked MIT code); the license text above is the text to carry.
Loading