Skip to main content

Boost Loss

CI Status Documentation Status

Test coverage percentage uv Ruff prek

PyPI Version Supported Python versions License


Documentation: https://boost-loss.readthedocs.io

Source Code: https://github.com/34j/boost-loss


Utilities for easy use of custom losses in CatBoost, LightGBM, XGBoost

Installation

Install this via pip (or your favourite package manager):

pip install boost-loss

Metadata

Release files for boost-loss 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for boost-loss 1.0.0
File Size Uploaded Provenance Actions
boost_loss-1.0.0.tar.gz 20.3 kB With provenance Details for boost_loss-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for boost-loss 1.0.0
File Interpreter ABI Platform Actions
boost_loss-1.0.0-py3-none-any.whl Python 3 none any Details for boost_loss-1.0.0-py3-none-any.whl

Total release size: 39.9 kB

Release files / boost_loss-1.0.0.tar.gz

Download URL boost_loss-1.0.0.tar.gz
Size 20.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d7dd37baef6d6cb73dc38a79c2c7378c978c2d62ae49b06e29485c1e517e2767
BLAKE2b-256 checksum
How to use checksums
6d726c53bc7d0d051abdf716ce7e7658e8b988cae8abb95eb392b24eed98fcde
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Nov 7, 2026.

Transparency log

Release files / boost_loss-1.0.0-py3-none-any.whl

Download URL boost_loss-1.0.0-py3-none-any.whl
Size 19.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a098cd765255cf5fb1a336d254dcdf21c0976881593e9afb39b72c674ce6b1e2
BLAKE2b-256 checksum
How to use checksums
d1d732b868882ee1156011590b1ee0c73215364635493e718c36bb06d6c9531c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Nov 7, 2026.

Transparency log

Security for boost-loss 1.0.0

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for boost_loss-1.0.0.tar.gz

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 Nov 7, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page