PyForeFire
PyForeFire provides Python bindings for ForeFire, an open-source wildfire simulation engine written in C++ and developed by CNRS at the Université de Corse Pascal Paoli.
The distribution is named forefire on PyPI; the importable module is
pyforefire.
Installation
pip install forefire
Wheels are published for Linux (x86_64, aarch64) and macOS (Apple Silicon and Intel), on CPython 3.9 and newer. They are self-contained: NetCDF and its own dependencies are bundled inside the wheel, so there is nothing to install beforehand and nothing to configure.
Installing also puts the forefire command-line interpreter on your PATH:
forefire -v
What the published wheels do not include
Wheels are built for portability, which means they deliberately leave out two build-time features:
- MPI coupling is disabled, so wheels cannot drive coupled fire-atmosphere runs with MesoNH.
- CPU-specific optimisation (
-march=native) is off, so the binary runs on any machine of the same architecture rather than only on the build machine.
If you need either, build from source (below).
Building from source
Any platform without a published wheel — Windows, musl-based Linux, or an unusual architecture — falls back to compiling the sdist, which needs a C++ compiler, CMake ≥ 3.15, and the NetCDF C and legacy C++4 libraries:
# Debian/Ubuntu
sudo apt install build-essential cmake libnetcdf-dev libnetcdf-c++4-dev
# Fedora/RHEL
sudo dnf install gcc-c++ cmake netcdf-devel netcdf-cxx4-devel
# macOS
brew install cmake netcdf netcdf-cxx
pip install forefire --no-binary forefire
To build with MPI support and native optimisation, pass the CMake options through:
pip install forefire --no-binary forefire \
--config-settings=cmake.define.FOREFIRE_ENABLE_MPI=ON \
--config-settings=cmake.define.FOREFIRE_NATIVE_ARCH=ON
If NetCDF lives somewhere CMake does not look, point at it with
--config-settings=cmake.define.NETCDF_HOME=/path/to/netcdf (and
NETCDF_CXX_HOME if the C++4 API is installed separately).
Usage
Verifying the installation
import pyforefire as forefire
ff = forefire.ForeFire()
ff.execute("FireDomain[sw=(0.,0.,0.);ne=(300.,200.,0.);t=0.]")
print("PyForeFire installed and domain created successfully.")
If this runs without an ImportError or linking error, your installation is
working. Note: you may see warnings about missing fuel tables, which is
expected at this stage.
Running a simple simulation
This example starts a fire in the centre of a domain and runs it for 1000 seconds.
import pyforefire as forefire
ff = forefire.ForeFire()
# 1. Define a 10km x 10km simulation domain
sim_shape = (10000, 10000)
ff.execute(f'FireDomain[sw=(0,0,0);ne=({sim_shape[0]},{sim_shape[1]},0);t=0]')
# 2. Set a simple propagation model (isotropic, i.e. a perfect circle)
ff.addLayer("propagation", "Iso", "propagationModel")
# 3. Start a fire in the center of the domain
ff.execute(f'startFire[loc=({sim_shape[0]/2},{sim_shape[1]/2},0.0)]')
# 4. Run the simulation forward by 1000 seconds
ff.execute("step[dt=1000]")
# 5. Print the state of the fire front to the console
print(ff.execute("print[]"))
This produces text output describing the location of the fire front nodes.
To generate a circle.kml file for visualization in Google Earth, set the
dumpMode parameter before the final print command:
ff["dumpMode"] = "kml"
ff.execute("print[circle.kml]")
More advanced examples
For examples that use real-world data (fuel, topography, wind), see the scripts
in the tests/python/
directory of the main repository.
Development
The Python bindings are built from the repository root, together with the C++ core:
git clone https://github.com/forefireAPI/forefire.git
cd forefire
pip install -e .
Re-run that command after touching _pyforefire.cpp or the C++ core. If you
iterate often, install the build requirements once and let scikit-build-core
recompile on import instead:
pip install scikit-build-core pybind11
pip install -e . --no-build-isolation --config-settings=editable.rebuild=true
To build a wheel without installing it:
pip wheel . -w dist/
The build is driven by scikit-build-core,
configured in the root pyproject.toml; the extension module target itself
lives in the root CMakeLists.txt behind FOREFIRE_BUILD_PYTHON.
Smoke testing a built wheel
python tests/python/test_wheel.py
Run this against an installed wheel rather than from a build tree: it checks that the extension loads, that its bundled NetCDF resolves, and that a trivial simulation advances.
Troubleshooting
NetCDF not foundwhile building from source: install the two NetCDF packages listed above. The C library alone is not enough; ForeFire'sDataBrokerincludes the legacy C++4 header<netcdf>, which ships inlibnetcdf-c++4-dev/netcdf-cxx4-devel/netcdf-cxx.Illegal instructionafter copying a self-built install to another machine: it was compiled with-march=native. Rebuild withFOREFIRE_NATIVE_ARCH=OFF, or use the published wheel.
License
ForeFire is licensed under the GNU General Public License v3.0. See the LICENSE file.
Project URLs
- Homepage: https://forefire.univ-corse.fr/
- Repository: https://github.com/forefireAPI/forefire
- Documentation: https://forefire.readthedocs.io/en/latest/
1 maintainer
Metadata
1 maintainer
Release files for forefire 2.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| forefire-2.5.0.tar.gz | 413.2 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 144.7 MB
Release files / forefire-2.5.0.tar.gz
| Download URL | forefire-2.5.0.tar.gz |
|---|---|
| Size | 413.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b158d56897465f64f2b87274529abeb33b2e4c3426c279f407ee02c3048bc84
|
|
BLAKE2b-256 checksum How to use checksums |
1f72b1f0ce1b872f75490763451f225f0bdb3273ccef0ab774d6f20dd64d8b9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
6d8448d069c2b3edf78921f3c255e72121aa81a9754e3b8ddb7bc21c675100d8
|
|
BLAKE2b-256 checksum How to use checksums |
4ea18709f312a690d946b5a7dd4ff4b52da2672fdf31210fed95c5aeac423aed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp314-cp314t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
f20108938394baab4bf2919ab55f3dbc44725391563f323cc50d2363b0cc8418
|
|
BLAKE2b-256 checksum How to use checksums |
dbc6449f2f9d53419a1b45703c2e4b118f7769527f50c56d2e7d50bbb3dedd49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314t-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp314-cp314t-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3998994409349703df7ca6c66b10ea1ae787ca58cfc19c8b70d06b5b905260ec
|
|
BLAKE2b-256 checksum How to use checksums |
b53b6e214d780ef2e6de07a643a4e9582f1401050957a0a948524f0accbfe105
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1e5017beeb42958025b1796ca5f3f630eacefb9d3396cf40e89575216f6815ff
|
|
BLAKE2b-256 checksum How to use checksums |
626f64fda79536588f2fec0692bcb8f7d3ce2d31532b0d8a7e8ab4a1e52836ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
4863f2f0f2a123935fe9d284a4e1bcc586163d7426a1938fa02d834866fa8ccc
|
|
BLAKE2b-256 checksum How to use checksums |
42221e8aac70f7420c2a478b07754bd815ce8333f85d6920cccde555ed8f4172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp314-cp314-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp314-cp314-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.14 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
354b05822bb6c4695b9abd71a82554848633b8285ad14dc35554784b3dc459af
|
|
BLAKE2b-256 checksum How to use checksums |
c74fbd11a1a5ba5e852974cefaedb041780f68788dce65f546e6aac5a6c2cf06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4e0e5222d9bedb28cce200a58dec7fc8022434ebc34fbcdb9fccc45dd00a167f
|
|
BLAKE2b-256 checksum How to use checksums |
87811892f213dee3e1f6d7a57015d8aa58e80647b2d94c9eeeb4573ce3c061c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ae69798df68bd8afcbc964e0f9835d1f751be3f91b3c48f552b19ea5fe664bcc
|
|
BLAKE2b-256 checksum How to use checksums |
094707c8df689d4e9ae69a9833ac376a02691149ac5afefd4ebaf908602dc833
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp313-cp313-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp313-cp313-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.13 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4fefa16f61d2133d549239da6eb7cdfc1e75b1acce4c4ab5ede1ae5e49d6dcd6
|
|
BLAKE2b-256 checksum How to use checksums |
cd3cb93d2f819cdd40026a413f30eefaadda963c2e0109f19c9b37a67fbc49c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0080954a8f6cc50ae447f503fb142ab7bf8134b82b03663516195f30f2550067
|
|
BLAKE2b-256 checksum How to use checksums |
d82c82ac7270a04e385e9fadd0cf0715408437d54b60f82a33db440bea529091
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
239a846f3773ee78e41b40d9f1b8baff1cda42b95d80dc64041dd0f0ef6d20c7
|
|
BLAKE2b-256 checksum How to use checksums |
edcd74b89b788e9cc8fccbf7469d4d0ab752785cc396a5bb1629d5375f4860da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp312-cp312-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp312-cp312-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.12 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8d69ccafb25d7b0dda2d9b796bfabfe8ca0a8a64edc02f1f9280144597a0f145
|
|
BLAKE2b-256 checksum How to use checksums |
1d0d0589094bdbb8f8bab8b28a9b6072615efc3b91e1e9ec3860a515fde74a02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5387f9885bdbd852608817994cd9681cd3266e931efc0a2eb185a6df9732c5aa
|
|
BLAKE2b-256 checksum How to use checksums |
02dd2ee8dfc3ff044728f480608eee0150895abb43c22f24ee5e62c4bac1917c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
50b64d462fcfd431beb4204104e8f0c5143c195b4e641f3a957663edf4d3b5d9
|
|
BLAKE2b-256 checksum How to use checksums |
06b4a8cb35218619830573aae4c478346e98de3c9fde6fd68be155bdbea3ca0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp311-cp311-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp311-cp311-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.11 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
55b6b9823bd402b7cd729d3e6a0a38a4a3252fac095f56fbeb616175d83261a1
|
|
BLAKE2b-256 checksum How to use checksums |
01cf5491a817fd0a6338a928b6e2a995c54ef5f58d01325b2e17f50eb16faafb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
08ff8c4c1ddc26a62c233157b68c19b8619cc1f3a00a41d3e3665901df0ff347
|
|
BLAKE2b-256 checksum How to use checksums |
0496d0825e43133f4a6b6a352addf0882a169290984bdc434fabdcdac5484ecb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
58ba937c93e72a64adddd88e376219114040ee82422593cb8a1d2510d2a0a9f5
|
|
BLAKE2b-256 checksum How to use checksums |
abe1ffc10e3e799f0b877959bcfe63494428d8aac29966f73a731170c6cc2c65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp310-cp310-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp310-cp310-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.10 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ef7d084f67cbefd589d7d5a540af1e8ce8634e64e9d3fa5cbdc531bc8bc8bc1a
|
|
BLAKE2b-256 checksum How to use checksums |
d7100264d08f5fb276843ea1fff956cb8aeaae74ead84d7e3b354d222474612a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | forefire-2.5.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5ea7a227b4c8b0a6f1f8e2ef282c439a8811ee86353785ea75c825e530d70d5e
|
|
BLAKE2b-256 checksum How to use checksums |
a803018b5f838e1a334d0f7ba3863d2c98dbde54213e702ebd4306fdfe5da201
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | forefire-2.5.0-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.6 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
deb97dec4aba9048b0bd83a265710738a553a5b8e9e46626e2d9483f9c123547
|
|
BLAKE2b-256 checksum How to use checksums |
f63448a4053c9faacf99094e0abeebb074a786efb25ed074eb9bd5ff2a6b77d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / forefire-2.5.0-cp39-cp39-macosx_14_0_arm64.whl
| Download URL | forefire-2.5.0-cp39-cp39-macosx_14_0_arm64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.9 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1d3bb3be1f8147b3a597a0572a4250482104416090609b7e2faf2881f2c2e9fd
|
|
BLAKE2b-256 checksum How to use checksums |
704fa3d372ca5c2102b7422a238dce37947754b83351745329d09f464abb0cde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logSecurity for forefire 2.5.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
All 22 files in this release have been uploaded with provenance metadata.
Attestation for forefire-2.5.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 Aug 11, 2026.
Transparency logA 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.
