LibreChessChess, explained simply

Third-party source and credits

Software Licences, Engine Source and Data Credits

LibreChess ships open-source engines, libraries, fonts and open chess data. This page identifies their exact versions, licence terms and source records without presenting the privately held LibreChess application source as open source.

On this page
  1. LibreChess first-party source
  2. Stockfish engine source and build provenance
  3. Libraries, Rust crates and fonts
  4. Chess data provenance
  5. How releases are checked
  6. Corrections
  7. Keep learning

LibreChess first-party source

The LibreChess application repository is private. LibreChess-authored source is maintained privately. It is not offered under a public source-code licence. This does not alter the licences or source-availability requirements of the third-party components below.

Stockfish engine source and build provenance

The browser engine files are GPLv3 software. For each deployed artifact, the release manifest records its byte length and SHA-256, the exact npm package and integrity value, the pinned browser-port source, the pinned Stockfish source, the build variant and the applicable full licence text.

Stockfish 18

LibreChess records this as stockfish@18.0.8, variant lite-single. The pinned source records the build command node build.js --single-threaded --lite -f with Emscripten 3.1.7. The npm package is fixed by its SHA-512 integrity value and git commit 93c994592dcf3b4b21052ab925e9b534df9c0918.

Pinned browser-build source archive · Pinned engine source archive · GPLv3 text

Stockfish Multi-Variant 2019-08-15

LibreChess records this as stockfish.js@10.0.2, variant single-threaded multi-variant WASM and asm.js. The pinned source records the build command ./build.sh. The npm package is fixed by its SHA-512 integrity value and git commit e105072e84cf8ee5dd5219e2c5be29c3b8bf8a5a.

Pinned browser-build source archive · Pinned engine source archive · GPLv3 text

Machine-readable records: engine manifest · corresponding-source instructions and checksums. The source record does not claim that an independent rebuild is bit-for-bit reproducible; the published artifact hashes define the files LibreChess deploys.

Libraries, Rust crates and fonts

The build inventories production npm packages, every external Rust crate in the WebAssembly validator’s resolved graph, the web-font packages, and the committed fonts used only to rasterise social cards. Unknown external licence identifiers or changed font hashes fail the compliance build.

Chess data provenance

The release verifier hashes each generated dataset output. A changed corpus cannot pass until its source record and checksum are deliberately updated. Large upstream objects and exact selection manifests are pinned where the build depends on them.

Download the machine-readable data provenance manifest. The lichess opening and puzzle sources are CC0; the pinned Figshare classic-game dataset is CC BY 4.0.

How releases are checked

Corrections

A wrong version, checksum, source link, attribution or licence classification is a material correction. Use the correction route; if no monitored destination is configured, that page says so explicitly.