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.

Metadata

Release files for XpongeCPP 0.2.15

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.15
File Size Uploaded Provenance Actions
xpongecpp-0.2.15.tar.gz 7.2 MB With provenance Details for xpongecpp-0.2.15.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for XpongeCPP 0.2.15
File Actions
xpongecpp-0.2.15-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for xpongecpp-0.2.15-cp312-cp312-win_amd64.whl
xpongecpp-0.2.15-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.15-cp312-cp312-manylinux_2_28_x86_64.whl
xpongecpp-0.2.15-cp312-cp312-manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.15-cp312-cp312-manylinux_2_28_aarch64.whl
xpongecpp-0.2.15-cp312-cp312-macosx_15_0_x86_64.whl CPython 3.12 CPython 3.12 macOS 15.0+ x86-64 Details for xpongecpp-0.2.15-cp312-cp312-macosx_15_0_x86_64.whl
xpongecpp-0.2.15-cp312-cp312-macosx_15_0_arm64.whl CPython 3.12 CPython 3.12 macOS 15.0+ ARM64 Details for xpongecpp-0.2.15-cp312-cp312-macosx_15_0_arm64.whl
xpongecpp-0.2.15-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for xpongecpp-0.2.15-cp311-cp311-win_amd64.whl
xpongecpp-0.2.15-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.15-cp311-cp311-manylinux_2_28_x86_64.whl
xpongecpp-0.2.15-cp311-cp311-manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.15-cp311-cp311-manylinux_2_28_aarch64.whl
xpongecpp-0.2.15-cp311-cp311-macosx_15_0_x86_64.whl CPython 3.11 CPython 3.11 macOS 15.0+ x86-64 Details for xpongecpp-0.2.15-cp311-cp311-macosx_15_0_x86_64.whl
xpongecpp-0.2.15-cp311-cp311-macosx_15_0_arm64.whl CPython 3.11 CPython 3.11 macOS 15.0+ ARM64 Details for xpongecpp-0.2.15-cp311-cp311-macosx_15_0_arm64.whl
xpongecpp-0.2.15-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for xpongecpp-0.2.15-cp310-cp310-win_amd64.whl
xpongecpp-0.2.15-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.15-cp310-cp310-manylinux_2_28_x86_64.whl
xpongecpp-0.2.15-cp310-cp310-manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64 Details for xpongecpp-0.2.15-cp310-cp310-manylinux_2_28_aarch64.whl
xpongecpp-0.2.15-cp310-cp310-macosx_15_0_x86_64.whl CPython 3.10 CPython 3.10 macOS 15.0+ x86-64 Details for xpongecpp-0.2.15-cp310-cp310-macosx_15_0_x86_64.whl
xpongecpp-0.2.15-cp310-cp310-macosx_15_0_arm64.whl CPython 3.10 CPython 3.10 macOS 15.0+ ARM64 Details for xpongecpp-0.2.15-cp310-cp310-macosx_15_0_arm64.whl

Total release size: 171.7 MB

Release files / xpongecpp-0.2.15.tar.gz

Download URL xpongecpp-0.2.15.tar.gz
Size 7.2 MB
Tags Source
SHA-256 checksum
How to use checksums
c248cc2ecbebd623962ece518e40ee33b1a8d81b6de69e0e9399a46d30348b09
BLAKE2b-256 checksum
How to use checksums
86784ac5943ef246ba062a0468f2ca1fe6bb4c18b0ff517b70bc533920a2bbf3
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-cp312-cp312-win_amd64.whl
Size 11.7 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
1808e9a4fb5ad8582e174ba9a4c309a41da5504a8c6a0b376f2b945814a5f734
BLAKE2b-256 checksum
How to use checksums
8a3551a4f10ff379c2d0fa8b0e2c1f84afc440fe53a7bf45f62bf0589f90eb09
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
3ea107fa74c22d7ec8fd87b4faeec7d3a46f0fb4f0bc7eb8b6e5e5368955f6f4
BLAKE2b-256 checksum
How to use checksums
e15832f13262f91af7133adf9eba908056e52602164961dbb77680069552c412
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-cp312-cp312-manylinux_2_28_aarch64.whl
Size 11.3 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
baa38334cb4355068fdf37f8843d35a03ff1709584c1bf0ee620a89ecb26ada3
BLAKE2b-256 checksum
How to use checksums
b709fbf0fafe48e2981a3704c2a8fce21e716a31191fbb60368061299495d747
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-cp312-cp312-macosx_15_0_x86_64.whl
Size 10.2 MB
Tags CPython 3.12 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
a8734542e7143f64a1e4454bc0ee50bb7b9ed6b8f9a4ed69eb153811df6e8676
BLAKE2b-256 checksum
How to use checksums
c9c4c53d68788cda62105d21c04e84edf870a0cf80aa6a8c0dbe22cf0fcbf70d
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
e21f593029cda3ccab759de1fe0312bb9f9c5cb2db4f2fa7b3c8fdb59933ec42
BLAKE2b-256 checksum
How to use checksums
31bcd3e5d4e9f409becf4b8725e6dc45c132510e5dba96df4c9e4cb3ac910e88
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-cp311-cp311-win_amd64.whl
Size 11.7 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
adf314c6b081bf2dd50e69d0a781119c91d5cb6a588c69f67f944641c843d5d1
BLAKE2b-256 checksum
How to use checksums
6c6a55d6e71488434cc277475d39b2f34c82b8ab0ecdc276762024b4680f207f
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
e53f204d622935df90dd5237eed4e013c4e7e28e3266a3515495b370647df748
BLAKE2b-256 checksum
How to use checksums
670cba64e5f2d8a75ff87cdf45ef088c1548afb941342d637ebe25b12e831a1a
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
9db8b69b911f579e135cc0d5eb91a9132bff7882a1f392f720eb12782275a8c9
BLAKE2b-256 checksum
How to use checksums
37f64761a440a2316691561d236c61fcd537dfb32036330754fd2ffd33b29606
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
782f063c2820a15d13a69e49f4805b313102cabea7d6beeaa39a1cd756fba5d3
BLAKE2b-256 checksum
How to use checksums
6417617e5b188e250d60f50d41ce16595e6e4ccd4c45d029e3e9e65bae4ef8d4
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
6a25c69312170e5f61a7ae68b5cadac8fdec1c46d8b1253765a12c208fc606d1
BLAKE2b-256 checksum
How to use checksums
062465f4d26bb1fe1c5e7fcc87bdc75476c7807a71facc0d1d52fbdc7b0f1315
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-cp310-cp310-win_amd64.whl
Size 11.7 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
463c94ade86c5427b79a660e5b6edc8c86c2c84189fba46257b51feb9af22865
BLAKE2b-256 checksum
How to use checksums
1f55c62f0ed44a78f5bbc540423f8367ce8ecd27bd55e1dec5b71710def67104
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
8fe937dbf10432c685198676ebfcd7ee40334aa626811e4dc9624d5b6110fcff
BLAKE2b-256 checksum
How to use checksums
8b769199a108a2de21d985e959168d4b037f5ecb1cc41ebb3a35a61aa34a44fa
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
7a732acfb1a06711069dd857da714fbfc2ea4d3347af90860dccda9241d0569b
BLAKE2b-256 checksum
How to use checksums
86d6a3a1cb3416d46a60fb94d3f6426ff20a5bfb842578050e9f6f34d04918ee
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
8dae7056975be2014ef814201e28b30f5ddde528b749b75d68a8a16bf4a362e2
BLAKE2b-256 checksum
How to use checksums
68156ca215f24fcd11c1c8bfb03719507917304b97c77f0cfb9d625e77e6a673
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 Oct 23, 2026.

Transparency log

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

Download URL xpongecpp-0.2.15-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
46c282869ac89941b87b42f7f6e1eed4bc2a7bd3bdf099b73a8182872e62a569
BLAKE2b-256 checksum
How to use checksums
f09706825149a868fa1cd811ec9c378957dd9d81e99c80143cee17b7e51e5d29
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 Oct 23, 2026.

Transparency log

Security for XpongeCPP 0.2.15

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.15.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 Oct 23, 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