Apheris Foundry SDK
Reference Python SDK for building Apheris Foundry per-module CLIs.
Usage
Declare a task — a plain function plus a pydantic config model — and foundry builds a typed CLI for it. See the usage guide to get started.
Development
This project uses pixi to manage the toolchain and environments.
pixi run install-dev # install the git hooks (pre-commit + commit-msg)
pixi run test # run the test suite
pixi run lint # check formatting and lint with ruff
pixi run fix # auto-fix formatting and lint issues
pixi run build # build the wheel and sdist
Commits follow Conventional Commits; the commit-msg hook enforces this via commitizen.
Project structure
src/apheris_foundry_sdk/ # SDK package
tests/ # test suite
docs/ # usage guide
License
This package is licensed under the Apheris Foundry Software License. The full license text is also included in every published distribution as LICENSE.
Support
Contact support@apheris.com for access and deployment assistance.
1 maintainer
Metadata
1 maintainer
Release files for apheris-foundry-sdk 1.0.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 | |
|---|---|---|---|---|
| apheris_foundry_sdk-1.0.0.tar.gz | 73.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apheris_foundry_sdk-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 162.2 kB
Release files / apheris_foundry_sdk-1.0.0.tar.gz
| Download URL | apheris_foundry_sdk-1.0.0.tar.gz |
|---|---|
| Size | 73.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f974b1dc6f1e339ee24c6258cf17feb578975e8a699a537c6bee4c3cd6653b1
|
|
BLAKE2b-256 checksum How to use checksums |
1f1274af37c7a18758ddf046a32a0daf38c79701385ab9508bc2c08fc9616bc7
|
| 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 Oct 8, 2026.
Transparency logRelease files / apheris_foundry_sdk-1.0.0-py3-none-any.whl
| Download URL | apheris_foundry_sdk-1.0.0-py3-none-any.whl |
|---|---|
| Size | 89.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5afd4d8c1230a63d82a7643a00adaf9a1bca12c027d083b27c8f5dae6f7ab4c6
|
|
BLAKE2b-256 checksum How to use checksums |
ed0445a69fd399b6ad6efdf9b7b700213d7fcad6a5271118ab6e706909e0dae6
|
| 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 Oct 8, 2026.
Transparency logSecurity for apheris-foundry-sdk 1.0.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 2 files in this release have been uploaded with provenance metadata.
Attestation for apheris_foundry_sdk-1.0.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 Oct 8, 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.
