Skip to main content

XpongeCPP

Preview beta: XpongeCPP is currently a preview release and is under active beta testing.

预览版说明:XpongeCPP 当前仍处于预览阶段,正在进行 Beta 测试。

Docs / 文档入口

XpongeCPP is a new C++ implementation of common Xponge workflows with a thin Python compatibility layer.

The original Xponge repository is used only as a reference implementation and regression baseline. This repository does not share the original Python object model internally.

Installation

PyPI-style installation target

The packaging target is:

pip install XpongeCPP

After installation, both of these should work:

import XpongeCPP
import Xponge

The wheel is configured to include both:

  • src/XpongeCPP
  • src/Xponge

so old Xponge package-name imports can continue to work after installation.

Automatic optional chemistry dependencies

The package now declares a practical default dependency set for pip users:

  • numpy
  • geometric
  • matplotlib
  • PubChemPy
  • MDAnalysis
  • rdkit
  • pyscf on non-Windows platforms
  • mokda-xpongelib (imported as XpongeLib)

Windows automatically skips pyscf through environment markers.

mokda-xpongelib is included so legacy gaff.parmchk2_gaff(...) workflows can resolve the XpongeLib bridge automatically after installation.

See:

GitHub Actions packaging matrix

The repository CI currently builds packages on:

  • Linux x64: ubuntu-24.04
  • Linux arm64: ubuntu-24.04-arm
  • macOS Intel: macos-15-intel
  • macOS arm64: macos-15
  • Windows x64: windows-2025

Validation is split into two layers:

  • all platforms run a minimal wheel smoke test with numpy installed
  • Linux x64 additionally runs a full dependency install smoke test

This keeps wheel validation broad across operating systems and CPU architectures without making every matrix job depend on the full optional chemistry stack.

v1 Scope

  • Amber-first force-field workflows.
  • Flat C++ storage with Molecule, Residue, and ResidueType view semantics.
  • Common Python entry points such as load_pdb, load_mol2, Add_Solvent_Box, Set_Box_Padding, Save_SPONGE_Input, and Assign.
  • Numeric equivalence goals for SPONGE input, not byte-for-byte compatibility.

Amber lipid force fields

Both Lipid17 and Lipid21 are packaged. Import exactly one lipid base family:

import XpongeCPP.forcefield.amber.ff14sb
import XpongeCPP.forcefield.amber.gaff2
import XpongeCPP.forcefield.amber.lipid21  # or lipid17

Either lipid import automatically registers the shared PI/phosphoinositide/LysoPL extension. Input remains Amber's split-residue representation, such as PA + SPM + SA; full lipid names such as PSM and POPC are not automatically split. The extension's mixed Lipid/GLYCAM/phosphate/GAFF2 provenance is reported when it is loaded.

Within one Python process, ff14sb/ff19sb, gaff/gaff2, and lipid17/lipid21 are mutually exclusive pairs. Different families may be combined; use separate processes to compare alternatives in the same family.

Development Environments

The lightweight development path still uses rtk uv:

rtk uv pip install -e . --force-reinstall --no-cache-dir
rtk uv run pytest -q

Full Assign validation needs optional chemistry backends. Use pixi for a reproducible environment with RDKit, PubChemPy, and PySCF:

pixi run install-dev
pixi run test-assign-full
pixi run test-resp
pixi run test

Bundled SPONGE HDF5 I/O is implemented in the native C++ backend. Its build dependencies match SPONGE: HighFive and the HDF5 C library. The pixi environment installs both automatically. Manual source builds must provide a discoverable HDF5 C installation; when HighFive is unavailable, CMake fetches the pinned HighFive 3.3.0 source archive automatically.

The default SPONGE input format remains the legacy raw-text layout. Bundled input v2 can be selected from the common API, while both format-specific entry points remain available:

XpongeCPP.save_sponge_input(molecule, "system", "inputs", format="bundle")
XpongeCPP.save_sponge_input_raw(molecule, "system", "inputs")
XpongeCPP.save_sponge_input_bundle(molecule, "system", "inputs")

Native topology export includes SW and EDIP pair/triple tables and atom-type indices. Custom listed forces can be declared with molecule.add_listed_force_definition(definition) (the usual [[[ name ]]] configuration), with their counted parameter rows supplied by a matching Molecule.Set_Save_SPONGE_Input(name) serializer. A listed_forces serializer may also supply the definitions. Definitions and data are parsed in memory and stored as typed HDF5 datasets, without text sidecars; custom modules can coexist with built-in Ryckaert–Bellemans terms. Missing data, conflicting definitions, and invalid parameter rows fail before replacing the output bundle. Minimum-bonded fake_mass, fake_LJ, and fake_charge remain unsupported.

For bundled input, pass a SpongeProtocol via protocol=. An RMSD ProtocolCollectiveVariable stores its reference_coordinates inline in protocol.spgp.h5 at /cv/<name>/coordinate: one finite XYZ row per selected atom, in atom_indices or atom_refs order. SPONGE continues to accept the old restart reference path; if both references are present, they must agree. Positional-restraint references remain in restart.spgr.h5.

bundle-to-legacy also exports native CV definitions and virtual atoms. RMSD reference coordinates are included directly as coordinate = ... in the generated CV file, preserving atom order and avoiding external reference files. Both inline protocol references and the old restart reference path are accepted; conflicting references or malformed coordinates fail before files are written. Disabled native objects are omitted. Legacy-to-bundle conversion retains these self-contained CV sections under /cv/config, so subsequent exports preserve their values.

RESP automatically selects the first available backend:

  • preferred backend: PySCF
  • fallback backend: Psi4
  • shared dispatch layer: XpongeCPP.qm

Example:

assign.calculate_charge("resp", backend="pyscf")
assign.calculate_charge("resp", backend="psi4")

from XpongeCPP import qm

qm.run_scf(assign, backend="pyscf")
qm.optimize_geometry(assign, backend="pyscf")

Windows does not install PySCF automatically. If a compatible PySCF is available, it is selected; otherwise install Psi4 separately as the fallback:

conda install -c conda-forge psi4
pip install XpongeCPP

PubChem network tests remain opt-in through the test environment; default Pixi tests use local mocks or dependency checks and do not require live network access.

Documentation

Packaging roadmap note

The current repository uses a hand-written GitHub Actions workflow plus scripts/build_pypi.py for packaging validation. We are deliberately keeping this simpler workflow for now because it makes the Xponge/XpongeCPP dual package layout and the minimal-vs-full smoke split easy to audit.

cibuildwheel is still a good future option once the wheel matrix and release policy stabilize further, but it is not the current default.

Explicit external parameters

See the explicit topology API for validated materialized parameters, per-atom LJ, and FEP replacement-molecule semantics.

Metadata

Release files for XpongeCPP 0.2.17

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

Source distribution (sdist)

Source distribution for XpongeCPP 0.2.17
File Size Uploaded Provenance Actions
xpongecpp-0.2.17.tar.gz 7.2 MB With provenance Details for xpongecpp-0.2.17.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for XpongeCPP 0.2.17
File Actions
xpongecpp-0.2.17-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for xpongecpp-0.2.17-cp312-cp312-win_amd64.whl
xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64 Details for xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_x86_64.whl
xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_aarch64.whl
xpongecpp-0.2.17-cp312-cp312-macosx_15_0_x86_64.whl CPython 3.12 CPython 3.12 macOS 15.0+ x86-64 Details for xpongecpp-0.2.17-cp312-cp312-macosx_15_0_x86_64.whl
xpongecpp-0.2.17-cp312-cp312-macosx_15_0_arm64.whl CPython 3.12 CPython 3.12 macOS 15.0+ ARM64 Details for xpongecpp-0.2.17-cp312-cp312-macosx_15_0_arm64.whl
xpongecpp-0.2.17-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for xpongecpp-0.2.17-cp311-cp311-win_amd64.whl
xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64 Details for xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_x86_64.whl
xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_aarch64.whl
xpongecpp-0.2.17-cp311-cp311-macosx_15_0_x86_64.whl CPython 3.11 CPython 3.11 macOS 15.0+ x86-64 Details for xpongecpp-0.2.17-cp311-cp311-macosx_15_0_x86_64.whl
xpongecpp-0.2.17-cp311-cp311-macosx_15_0_arm64.whl CPython 3.11 CPython 3.11 macOS 15.0+ ARM64 Details for xpongecpp-0.2.17-cp311-cp311-macosx_15_0_arm64.whl
xpongecpp-0.2.17-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for xpongecpp-0.2.17-cp310-cp310-win_amd64.whl
xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64 Details for xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_x86_64.whl
xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_aarch64.whl
xpongecpp-0.2.17-cp310-cp310-macosx_15_0_x86_64.whl CPython 3.10 CPython 3.10 macOS 15.0+ x86-64 Details for xpongecpp-0.2.17-cp310-cp310-macosx_15_0_x86_64.whl
xpongecpp-0.2.17-cp310-cp310-macosx_15_0_arm64.whl CPython 3.10 CPython 3.10 macOS 15.0+ ARM64 Details for xpongecpp-0.2.17-cp310-cp310-macosx_15_0_arm64.whl

Total release size: 171.9 MB

Release files / xpongecpp-0.2.17.tar.gz

Download URL xpongecpp-0.2.17.tar.gz
Size 7.2 MB
Tags Source
SHA-256 checksum
How to use checksums
a7945147604398348d9780db6387838b0a9ca478b12d2680d5218e22e2c826eb
BLAKE2b-256 checksum
How to use checksums
14bb39d720fb70b39d300d82ff2dc3f87afb6fbd2ae9209d66be9ea2ae5859cc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp312-cp312-win_amd64.whl

Download URL xpongecpp-0.2.17-cp312-cp312-win_amd64.whl
Size 11.7 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
54ee43178c0b4af68900095e40be42f952884fc5bff0a4d4fe2b22e71164fe14
BLAKE2b-256 checksum
How to use checksums
4f042a6e3f43b0bdd90a6aebd5d0b1bc73d7095acaee4a0e810f469232056e83
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_x86_64.whl

Download URL xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_x86_64.whl
Size 11.0 MB
Tags CPython 3.12 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
9d19503055c33d0b9887a932e4c633e39fe57d4377b67a3db8446afef9e76730
BLAKE2b-256 checksum
How to use checksums
ab3e382bfc191a0263a8ed4e46fb2bad6ad93dfd6743fcfd6ff66f680564b578
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_aarch64.whl

Download URL xpongecpp-0.2.17-cp312-cp312-manylinux_2_28_aarch64.whl
Size 11.4 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
26813571f6109bf479404788fd3e46f9db3cda6a261d303c5dd35dfaf4fd9294
BLAKE2b-256 checksum
How to use checksums
bcb3f264f50a65282a1593fafff3ab4d02c34a559008725e089f9e56bb8f134a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp312-cp312-macosx_15_0_x86_64.whl

Download URL xpongecpp-0.2.17-cp312-cp312-macosx_15_0_x86_64.whl
Size 10.3 MB
Tags CPython 3.12 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
7a271bb611423a7f749a7935e1407de913ca2b8fbe423436611ffcc4469cfd8b
BLAKE2b-256 checksum
How to use checksums
9448ad8a5f117fd0188e1354d7c4f394069ae031dfee574c165ec2e7ef3a87fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp312-cp312-macosx_15_0_arm64.whl

Download URL xpongecpp-0.2.17-cp312-cp312-macosx_15_0_arm64.whl
Size 10.6 MB
Tags CPython 3.12 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
e1316abcc21d000f91867eb6db220f3b200da769f42839f573a543e0db603df2
BLAKE2b-256 checksum
How to use checksums
bcb5789757c6940416970bda9f6df23392e9828c02b6a88245818c3c9c0f7aba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp311-cp311-win_amd64.whl

Download URL xpongecpp-0.2.17-cp311-cp311-win_amd64.whl
Size 11.7 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
234f6101830ad9f6e2fd541952c2d400a6c658fe70a51a80e253e4ff0d084439
BLAKE2b-256 checksum
How to use checksums
c54511ac829a6c95a5fa036df1102e99d74a3a199a1f61e484ed575a3f4fde0d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_x86_64.whl

Download URL xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_x86_64.whl
Size 11.0 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
62020c12b6582d08b3b52be0f9860a4b51ac32d1e535e9543ca286bca2f116ec
BLAKE2b-256 checksum
How to use checksums
611d1f700c7911c9158a10bcd254f8be98a884536adcd92c8f0f689329c18242
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_aarch64.whl

Download URL xpongecpp-0.2.17-cp311-cp311-manylinux_2_28_aarch64.whl
Size 11.3 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
963552bda6c8f361eca6cedf7b33b3aa1301788135712eedb2ce2e508dbffb0e
BLAKE2b-256 checksum
How to use checksums
e52b6b5107c65945f77cc842798cff0729882dd7648f290e6aaef142c9c3affd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp311-cp311-macosx_15_0_x86_64.whl

Download URL xpongecpp-0.2.17-cp311-cp311-macosx_15_0_x86_64.whl
Size 10.2 MB
Tags CPython 3.11 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
16effcb8cad326e663263314e453f96de6ec3989a4ee4160662b8992aeb59a6f
BLAKE2b-256 checksum
How to use checksums
3e116459acd7c2ff65327e0e08a09910c77bf472d4edb58819ed8ce83fad2643
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp311-cp311-macosx_15_0_arm64.whl

Download URL xpongecpp-0.2.17-cp311-cp311-macosx_15_0_arm64.whl
Size 10.6 MB
Tags CPython 3.11 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
698b88b48956a1c09393bf7b1f56f0f9aa7de22c5937d73297a055e0bc469a20
BLAKE2b-256 checksum
How to use checksums
2a1c979d5fb95d46694ca4499ef1bcb54828e364b7cc76de55ce3f54a6ba772f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp310-cp310-win_amd64.whl

Download URL xpongecpp-0.2.17-cp310-cp310-win_amd64.whl
Size 11.7 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
d4cbc749f5663d8c08d92b8f983ac878159629be9a2659811a765c00f2ef501c
BLAKE2b-256 checksum
How to use checksums
6038b70ba05e1c1c1a37ed6c453470a47c991fe449addedad7f0769f16b64066
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_x86_64.whl

Download URL xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_x86_64.whl
Size 11.0 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e54229c427233cdc9a877b537a8bee5bd8a7ca8eb36cd9a348ce368f643ddc8a
BLAKE2b-256 checksum
How to use checksums
7605e13e62c57d03ccd9c71316a59f99984f0462900110ec024c11aeb5053b60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_aarch64.whl

Download URL xpongecpp-0.2.17-cp310-cp310-manylinux_2_28_aarch64.whl
Size 11.3 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
6588216fc84932ba93512637ade8247b123484fbe015cb8620f6b4d9b441aed9
BLAKE2b-256 checksum
How to use checksums
99dd9cd86a0fd33be64df5a65cfc3f2462add0bf409ae031b8d13b1d0b9d96e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp310-cp310-macosx_15_0_x86_64.whl

Download URL xpongecpp-0.2.17-cp310-cp310-macosx_15_0_x86_64.whl
Size 10.2 MB
Tags CPython 3.10 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
4159dca8471d4fb6f29b65f8be0104ef40bf5fefbaa6f5b77b17f529c44dc25f
BLAKE2b-256 checksum
How to use checksums
2934332902f174eb97e07f5057c24429ebdad2ca14700ccb4fc0d2f16b506ea6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / xpongecpp-0.2.17-cp310-cp310-macosx_15_0_arm64.whl

Download URL xpongecpp-0.2.17-cp310-cp310-macosx_15_0_arm64.whl
Size 10.6 MB
Tags CPython 3.10 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
930a599b2a33262d1efecbd749281d67a2e99ab11f66630af228d1507b58205f
BLAKE2b-256 checksum
How to use checksums
95a1f01531cb720002b305dbe49186a2d26d03ce14e55eee3ef60243fd1baff7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Security for XpongeCPP 0.2.17

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

All 16 files in this release have been uploaded with provenance metadata.

Select from 16 files

Attestation for xpongecpp-0.2.17.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 17, 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