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.16

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

Built distributions (wheels)

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

Total release size: 171.9 MB

Release files / xpongecpp-0.2.16.tar.gz

Download URL xpongecpp-0.2.16.tar.gz
Size 7.2 MB
Tags Source
SHA-256 checksum
How to use checksums
ae35babdcaddd8d25611d1bf9a791ed04f8e5cd36fd884992f05fd0d72c35fd4
BLAKE2b-256 checksum
How to use checksums
9ec9a5ba468fbd4955cf67233647e699770d3ee06f4cd15b510748226dc4472f
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-cp312-cp312-win_amd64.whl
Size 11.7 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
f68c4ddd725f76ae12754512487e1b048daae5ba89633755a5c49446d9d8d2a3
BLAKE2b-256 checksum
How to use checksums
77e65aab4a5f1a6eb8cc7a1dc9a610cd930b185c8d6b58fc2290cf08a2e698a9
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
3351597b3b3a7b26541e907639f0bb200bd7b508b00246b6b1629aad270c73a6
BLAKE2b-256 checksum
How to use checksums
399a9e7e374e3ea22134eae6e464886786604c7d249d0c3ef29683dc5b94070c
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
89fa860fa74390d82c872a7a0b5920174082fe17b90011f70f03a2027ee05d7d
BLAKE2b-256 checksum
How to use checksums
02ee973e8094314b5ed954b565ac4cb0adb0942cbbf7e09f75e441641577750f
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
05fe4c0f985577694e1aea0aaceabef2b13fcf5a1d3b76055f67fde694f00caf
BLAKE2b-256 checksum
How to use checksums
4de653f7eba44fbc68e244329871fdd7f4ca945291cb8d79f046b5d8ebd1b39b
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
5d52e754e5a9e1b0412fe1cd7cadc8a8752a79728dfd1a295c01dd9c07360b23
BLAKE2b-256 checksum
How to use checksums
a02f7ae8280503db16639457eeda4f8638363a38c12b014a70e6ef7851542355
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-cp311-cp311-win_amd64.whl
Size 11.7 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
dd83f786a26f8b86045b9b289fde71be0a769f53bff4f6d5e312e95d83455092
BLAKE2b-256 checksum
How to use checksums
00c07729b6bfa45e10cab92d7ed1373fd5fd4f965b8ebf46aa72a4646ceab723
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
0d61981008f7b98ec8d86711cf3c4a7ad9f2c1417701ee8325442757bc6d8d4d
BLAKE2b-256 checksum
How to use checksums
148313fb8fc81d05ddcfe85b25f1917240343ed3bbdb509aef9504ee585e7ff5
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
124f899d5117800525fb0f842a944a5101017d36b943dc5f2c79c6d88b761e9f
BLAKE2b-256 checksum
How to use checksums
a15c9921bfaefcb7a452332a1d556a3c2dd79bbdbd83a5d06e7f54ef2ffafb2e
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
6771e40c7ff49844809723040d39a6aa3e71d89b230051ca18745523b713a5d4
BLAKE2b-256 checksum
How to use checksums
1f3e7893d11b2933a18a8b44b480c7fc0bcd3f157bd6f0998916d11afa090de8
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
3e8c6106e5d5eff13909fc6a405ac5a3580a063d84955f9feb9b100da9e54c86
BLAKE2b-256 checksum
How to use checksums
dc8cd82ac7f90b97dfe9c5ea30bd3dee449621bec4156e0ee23b8154a30c7bf3
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-cp310-cp310-win_amd64.whl
Size 11.7 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
5f7c5f80aa3d748d61df86bd1956a009423018ef19632acaf3e5a56af4242ec3
BLAKE2b-256 checksum
How to use checksums
1ebc81b7bf2926446fd7a10d6292fe7b15c88f508f4db7ab965a066c3159049b
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
60366dda457f9f6cf78c7c47d533027f0cafc6c88cf044693289fe31d6daab55
BLAKE2b-256 checksum
How to use checksums
a6929f6fada528ab7fdac115e94226cf83623c62cdd4dfe0b890ec8614b04590
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
845fdadea2b8b0f6737265c7f13fdedf25f46234fa5a8eb7c1dfb481e884cd99
BLAKE2b-256 checksum
How to use checksums
269633e5dc839f53a69d94f5bb7d9385c06b90d4a95a3d6aa1d82fd1081ace88
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
6964c61733a4a7f953f57098fe140813c6889f5748024687dc14289657cfcaa0
BLAKE2b-256 checksum
How to use checksums
2405c79b02b3dbde3de0aecc0db344d3ddf8a1df9898ae24407aea45e0f5b5f4
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 5, 2026.

Transparency log

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

Download URL xpongecpp-0.2.16-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
89050589cc9568068f25d5176af463793948b254edf87e19b2bf9ff3a072e1fb
BLAKE2b-256 checksum
How to use checksums
807f62174bbbf4db64bae33a76e3d09407bb5ffe7e83f0f11fe22fb5dd0ac2b6
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 5, 2026.

Transparency log

Security for XpongeCPP 0.2.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.

Full provenance

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

Select from 16 files

Attestation for xpongecpp-0.2.16.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 5, 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