FL-Net Python Tool API
pip install "FL-Net-Python-Tool-API~=0.7.12"
The package is imported as pyfedappwrap (from pyfedappwrap.engine.runtime import FedDBEngine).
Use the distribution name FL-Net-Python-Tool-API in dependency files; pyfedappwrap
is the Python import name.
Python SDK and runtime for building FL-Net tools ("apps"): local analyses, preprocessing/transformer
steps, exports and federated learning apps. You implement the logic; pyfedappwrap handles the communication
with the platform, app.yml configuration, metrics, result upload, login during development and federated
aggregation (including SMPC and differential privacy settings).
Part of FL-Net, the federated learning platform also behind PosyMed.
Documentation
All documentation can be found on the FL-Net documentation site:
- FL-Net documentation
- Federated runtime: how the engine runs a federated run internally
Development
pip install -e ".[dev]"
pytest
| Folder | Content |
|---|---|
pyfedappwrap/ |
The package |
tests/ |
Test suite, with test apps in tests/apps/, configs in tests/configs/ and input data in tests/data/ |
examples/ |
Example apps for tool authors |
scripts/ |
Local dev runners, started from the repository root (python -m scripts.run_local) |
docker/ |
Base image Dockerfiles, built by .github/workflows/docker.yml (Dockerfile.local: local builds only, see dev_scripts/) |
dev_scripts/ |
build_local_docker_image.sh: builds base-python-dep:testingtag with this checkout, to test Tool API changes in the FL-Net-Sandbox |
Local settings go into .env (template: .env.example).
Develop builds
develop carries the next version as X.Y.Z.dev (.github/scripts/version.sh), like all FL-Net repositories.
Every push to develop that changes the package is published to TestPyPI as X.Y.Z.dev<run>, since package indexes
never take a version twice, and all base images are rebuilt with it under the moving tags X.Y.Z.dev and staging.
A tool tries unreleased changes without a merge to main:
FROM ghcr.io/fedlearnnet/python-tool-api/base-python-dep:0.7.15.dev
Only the SDK comes from TestPyPI, its dependencies come from PyPI.
License
Apache License 2.0 © Institute for Computational Systems Biomedicine and contributors.
1 maintainer
Metadata
1 maintainer
Release files for FL-Net-Python-Tool-API 0.7.16
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 | Actions |
|---|---|---|---|---|
| fl_net_python_tool_api-0.7.16.tar.gz | 153.1 kB | With provenance | Details for fl_net_python_tool_api-0.7.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fl_net_python_tool_api-0.7.16-py3-none-any.whl | Python 3 | none | any | Details for fl_net_python_tool_api-0.7.16-py3-none-any.whl |
Total release size: 300.3 kB
Release files / fl_net_python_tool_api-0.7.16.tar.gz
| Download URL | fl_net_python_tool_api-0.7.16.tar.gz |
|---|---|
| Size | 153.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
429721b5d19225c0104485177e96b647f72d04ebb0446631c597723ebdf7a5a1
|
|
BLAKE2b-256 checksum How to use checksums |
f5b6007e941f7fcad121644c46e02bb1c5c990fbc89c0a40c3f7623050f1c435
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Nov 10, 2026.
Transparency logRelease files / fl_net_python_tool_api-0.7.16-py3-none-any.whl
| Download URL | fl_net_python_tool_api-0.7.16-py3-none-any.whl |
|---|---|
| Size | 147.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bcc62cf0d45df841e51f80fc4c73290f3f91da23255ef05a236cd8ea51a4c814
|
|
BLAKE2b-256 checksum How to use checksums |
d40559afc00133c757e459ca6c5c07d4f5bbbb4863272ff651521de10ab2fe53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Nov 10, 2026.
Transparency logSecurity for FL-Net-Python-Tool-API 0.7.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
Both files in this release have been uploaded with provenance metadata.
Attestation for fl_net_python_tool_api-0.7.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 10, 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.
