Skip to main content

HexBug-data

Standalone registry code and parsers for HexBug, a Discord bot for Hex Casting.

This is published to PyPI for use in projects which would like to use HexBug's registry as a data source.

Getting the data

Pre-built dumps

Registry dumps are uploaded to the Book of Hexxy for each release (eg. https://book.hexxy.media/v/2.4.0/registry.json). The registry.json file can be imported using HexBugRegistry.load().

Building

If you'd rather build the registry yourself, you'll need to install HexBug-data with the full extra. Since many addons are not currently published to PyPI and certain addons have incompatible dependencies, constraint files are uploaded to the Book of Hexxy for each release:

For example:

uv pip install HexBug-data[full] --overrides constraints.txt

Depending on the version, you may also need to install some packages from HexBug's vendor directory.

After installing, you can build the registry from scratch using HexBugRegistry.build().

Metadata

Release files for HexBug-data 2.8.2

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

Built distribution (wheel)

Table of built distributions (wheels) for HexBug-data 2.8.2
File Interpreter ABI Platform Actions
hexbug_data-2.8.2-py3-none-any.whl Python 3 none any Details for hexbug_data-2.8.2-py3-none-any.whl

Release files / hexbug_data-2.8.2-py3-none-any.whl

Download URL hexbug_data-2.8.2-py3-none-any.whl
Size 37.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c9816237af19e0207d2c6420c5688ae92dfe5b91d0debfe988a505413ecd1ec1
BLAKE2b-256 checksum
How to use checksums
5b0847bc2bb6670edd51170c7aa9924cff96a2e30a380bbe3740a9a173789227
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 11, 2026.

Transparency log

Security for HexBug-data 2.8.2

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

1 file in this release has been uploaded with provenance metadata.

Attestation for hexbug_data-2.8.2-py3-none-any.whl

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 Mar 11, 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