The Open Sage Backgammon Bot Engine Library
Open Sage is a "backgammon bot engine" - that is, a library that you can ask questions like "what's the best move in this situation, with all the analytics to back it up", or "is this a double, and if so, is it a take or a pass (including analytics)?".
What it Contains
It is a joint Python/C++ library that includes:
- A neural network-based backgammon bot.
- Neural network training framework using both self play and supervised learning, including training code, benchmark scoring, with customizable inputs. Uses your NVIDIA GPU (via CUDA) if you have one.
- The post-training weights for several different versions of the bot engine.
- Multi-ply and rollout calculations that efficiently parallelize on the CPU. Full technical specifications of the algorithms are in MULTI-PLY.md (N-ply search and the cubeful evaluation engine) and ROLLOUT.md (truncated and full rollouts with variance reduction).
- Test framework.
- VIBING.md: information on how to use Claude Code-style tools to interact with and change it, and how to submit changes back to us (the maintainers). Most of this code was written by Anthropic's Claude Code and OpenAI's Codex.
What Evaluation Levels Does It Support?
The library supports "multi-ply" lookahead calculations. 1-ply is the raw neural network evaluation (we follow the XG/eXtreme Gammon numbering convention; GNUbg calls this "0-ply"). Adding a ply makes the calculation roughly 20x slower. It efficiently parallelizes these multi-ply calculations on your CPUs.
It supports truncated rollout calculations, where it simulates the game several turns into the future and then stops the simulation, using bot evaluations at the leaves.
It also supports full rollout calculations, which are simulations playing out the game over and over to completion.
Truncated and full rollouts both include variance reduction and efficiently parallelize on CPUs.
What are Its Interfaces?
It offers both Python and C++ interfaces for:
- Checker play analytics: given a list of checker positions, the two dice, and cube information, it returns you a list of information about the top possible moves, sorted in descending order of equity; for each it gives you equity and cubeless post-move probabilities. You can specify the evaluation level.
- Post-move position analytics: given a list of checker positions and the cube information, it returns you cubeful equity, cubeless equity, and the cubeless probabilities - for a post-move position (right before the opponent's turn).
- Cube action analytics: given a list of checker positions and the cube information, it returns you cubeful equity information about the three states (ND, D/T, and D/P), cubeless equity, and the cubeless probabilities - for a pre-roll position.
- Game plan classification: given a list of checkers, it returns the optimal game plans of the player and the opponent.
- Game utilities (flip a board, etc).
How Does it Compare to XG?
We tested money games and match play against eXtreme Gammon (XG), another popular backgammon analysis application. In particular, we tested Open Sage's 3T evaluations (truncated rollouts) to XG Roller ++ (an equivalent truncated rollout). The two bots were very close, with some weak evidence that Sage 3T is a bit stronger.
Details of the tests, and instructions on how to replicate them, are in XG_COMPARISON.md
License
Open Sage is released under the Mozilla Public License 2.0 — see LICENSE.
That covers everything in this repository, including the trained model weights in
models/ and the bearoff database in data/. Those aren't source code, so to be
unambiguous: they are licensed on exactly the same terms as the code, and you are free to
use them in a commercial product.
In plain English:
- You can use Open Sage in a commercial, closed-source product. Import it, link it, bundle the weights, ship it. Your own code stays yours, under whatever license you choose.
- If you modify a file that came from Open Sage and distribute it, publish that file's source under the MPL, so the improvement comes back to everyone. Files you write remain entirely yours, even when they sit right alongside ours.
- Private use carries no obligations at all. Experiment, retrain, tinker — if you aren't distributing it, nothing is asked of you.
The MPL is file-level copyleft, so the obligation is narrow and predictable: it attaches only to the files you changed, and never to the code you build around them. If you do improve the engine or train better weights, a pull request is very welcome.
1 maintainer
Release files for bgsage 1.5.20260813
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bgsage-1.5.20260813.tar.gz | 68.0 MB | Details |
Built distributions (wheels)
Total release size: 240.5 MB
Release files / bgsage-1.5.20260813.tar.gz
| Download URL | bgsage-1.5.20260813.tar.gz |
|---|---|
| Size | 68.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
624e9f83bcc386f229a5f7ae1c90176e5a4196da17c96a40c5baee1ec664e923
|
|
BLAKE2b-256 checksum How to use checksums |
c077ad413e40bf4a827e496e4355a29145a5464f5b90e436a01a665b62380de7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp314-cp314-win_amd64.whl
| Download URL | bgsage-1.5.20260813-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b4198a8399719db097cd687e64cc283ed9568a8715ac0dc73711b3d8e70e4391
|
|
BLAKE2b-256 checksum How to use checksums |
5204efeb79930e1f002ffdb4129f2110e12c8e82e497cd6b1e21f28ea557eb59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
785cfc52de4ec30986bb7e72ac8906f4acb3439be7d778db13ba5f1fb12e435c
|
|
BLAKE2b-256 checksum How to use checksums |
744abbc198ae54b6b3a150546bd350c27b5632cea0a56611537dff1dd6a35b1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | bgsage-1.5.20260813-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0f5bceab933f874920a4ea0317efad5ebf42fdc654961adbc3bf24b266e1b76b
|
|
BLAKE2b-256 checksum How to use checksums |
b631c7426229e150904ec26c8f485f02df804372d1a560f4882c57e89bf9a101
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8ed11c2265b6483c5f2ad9e748b44c0e4ded2c5202322c4b86e62958774ef26
|
|
BLAKE2b-256 checksum How to use checksums |
14ba18762249af2086263837f5a30373a624f8ec21464cde5c92607261c16e1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp313-cp313-win_amd64.whl
| Download URL | bgsage-1.5.20260813-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
08550cc58a9cbc44ebe68bd6eee0274f3d02a9744effd50b226bb45d9abf7830
|
|
BLAKE2b-256 checksum How to use checksums |
7e6e3771f96bea0fda791d692cab093c05646ba820648b277ea60509cad9e285
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
738223a9fedb4a65e27af9ea233c9f21190b6706ab2644988cb7a9a3d8f2c7ea
|
|
BLAKE2b-256 checksum How to use checksums |
4a4c01cbda43e8eeeababd184d739831d334e52a1f935fd9a06a9ee845237568
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | bgsage-1.5.20260813-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
44e4fe20fc1aa3e8da1fc8d709f0bd3112a276b1a8d61501cdd72fb1275a2759
|
|
BLAKE2b-256 checksum How to use checksums |
4663c0468a43e93f0a6eb6a9999b36dffee2c216645fae769cca57e504a31cab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
816b9d976a75f37ca475fbaaf0d3e8f0eb0571f3d933626ba503625aa78a9bdb
|
|
BLAKE2b-256 checksum How to use checksums |
9eb8ed458f6f65cd6c8dd415092e3932e101266393c2d84eca9bd480c6b5c52c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp312-cp312-win_amd64.whl
| Download URL | bgsage-1.5.20260813-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9bdc92c5c39ac2448f077b0c623893f2298ac6a6273311fb201a6d982a5fa910
|
|
BLAKE2b-256 checksum How to use checksums |
2a464c523a7e9e57f9c55b26678fa48accd5d16873ede03bfefbb5d6dae59db3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
94d388a88d0c98835a443e6b45f40186b43209de3a9b7a0b6b426984fe45f607
|
|
BLAKE2b-256 checksum How to use checksums |
e3bdb6a16fe322ca89e2ae0a6e2c790fbf475eacf39e106585c989559878a294
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | bgsage-1.5.20260813-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9b66396a69764f503321e52205a3e4f94b98672182373e26cdd3abcb84616072
|
|
BLAKE2b-256 checksum How to use checksums |
f4357e1c37ca5120976de480501abff1f68d72cd57daa9c72b0ef917cc8e6662
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
de92b1b0336c1e47c8547ed98b2ff5f56deaa8c2f39d2b8d4510cff3fa7f7cbc
|
|
BLAKE2b-256 checksum How to use checksums |
e54563ab7fd39b8c0676fb31801e0407bded1f3cd4ab30fdefd8b85073f062c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp311-cp311-win_amd64.whl
| Download URL | bgsage-1.5.20260813-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6f519464fae859f05ab77a4dbb8ffa3a953db78304263a3aafcb3e9c061341e1
|
|
BLAKE2b-256 checksum How to use checksums |
92724c24f794554912acb21fa8d530c27dea316a6904edeaad5ada869610c8d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
c792b8c5265fe70e4ee6cf25e473379bf622fa8d88a6af42b6e16164fb008133
|
|
BLAKE2b-256 checksum How to use checksums |
3e7e75a2f21474cc2e88d1ed5814fc4729b18202f060abc4b5c33bdba1fb0e9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | bgsage-1.5.20260813-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d900cbb0abcdd2ae1b52a174ec54302ac232bd31a4e3f9f3e8e235d0527938f9
|
|
BLAKE2b-256 checksum How to use checksums |
6ed173956844efdbaaffd6aaa0765257103b41ca51f5905d444ba796a7b2b9a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
da2fbb6f6e613760d09604560e7b384e3e44b5a8ffa79515943d1997c169e912
|
|
BLAKE2b-256 checksum How to use checksums |
f79882254b1d21483ef9e8bbda55bd48cf87d6d22d35186b87d87a27001ea5d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp310-cp310-win_amd64.whl
| Download URL | bgsage-1.5.20260813-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6ddd15cdff863c0e7bd4678bd190686d9fc1da0c14ed787656e5f28ce3f70703
|
|
BLAKE2b-256 checksum How to use checksums |
63afa96ee95ab4151cb1291824f8848b9641999fdb9b2b21faf8e00c7f9dc62c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9dbf6025c40b8a31dc47b4b70a6d45ddbc794d8330062c639a8a85eb5f2a2353
|
|
BLAKE2b-256 checksum How to use checksums |
9c7eae571f21b1264990e5af89240a2c9cadf82c616d329c7c0240eab7252450
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | bgsage-1.5.20260813-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0062516a538d9acab118a72a484d0b6dd4d76dffb72c0843578a05b923573b4a
|
|
BLAKE2b-256 checksum How to use checksums |
b55559f1e629793dea3753b34aae7409062a2f57e8618d04e7568c0b3da14136
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / bgsage-1.5.20260813-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | bgsage-1.5.20260813-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
82e58a33c10f10a1e9de1db2938d16b8decc6c7ce85fd40ddae0e88fb8e83b1b
|
|
BLAKE2b-256 checksum How to use checksums |
40f2e04943788f88a97f358aeb07164b5cb605dcee76f44eeae52f3fc155c8e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency log
