Exordos SDK
📚 Documentation: exordos.github.io/gcl_sdk
Exordos SDK is a set of tools and libraries for developing Exordos elements. It provides the building blocks needed to integrate your own services and capabilities with the Exordos Core platform — from event handling and auditing to universal agents, builders, and schedulers.
What Exordos SDK does
Exordos SDK hides the complexity of interacting with the platform and lets element developers focus on their domain logic.
Key components:
- Universal Agent — a ready-to-use agent runtime with a pluggable capability driver model for managing services, load balancers, SSH keys, secrets, machine pools, and more on any node.
- Universal Builder — a framework for describing and building infrastructure and application topologies in a declarative way.
- Universal Scheduler — a scheduling component for orchestrating element lifecycle operations.
- Events — a unified API for publishing and consuming Exordos events with pluggable payload models.
- Audit — built-in support for recording and exporting audit trails.
For a full overview of components, quick start guides, and advanced usage, visit the documentation.
🔗 Related projects
- Exordos Core is the main project of the Exordos ecosystem. You can find it here.
- Exordos CLI is the official command-line interface for the Exordos Core platform. You can find it here.
💡 Contributing
Contributing to the project is highly appreciated! However, some rules should be followed for successful inclusion of new changes in the project:
- All changes should be done in a separate branch.
- Changes should include not only new functionality or bug fixes, but also tests for the new code.
- After the changes are completed and tested, a Pull Request should be created with a clear description of the new functionality. And add one of the project maintainers as a reviewer.
- Changes can be merged only after receiving an approve from one of the project maintainers.
Metadata
Release files for gcl-sdk 3.7.1
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 | |
|---|---|---|---|---|
| gcl_sdk-3.7.1.tar.gz | 383.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gcl_sdk-3.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 723.2 kB
Release files / gcl_sdk-3.7.1.tar.gz
| Download URL | gcl_sdk-3.7.1.tar.gz |
|---|---|
| Size | 383.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad68a260ffa21744fd47dbe0b60a01ad2d255b420de8f6e65a02afd189a79268
|
|
BLAKE2b-256 checksum How to use checksums |
f292df520ed55e40fef1e91c2569f08161d0e5dc14f82a56922cfde5bd06a57b
|
| 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 21, 2026.
Transparency logRelease files / gcl_sdk-3.7.1-py3-none-any.whl
| Download URL | gcl_sdk-3.7.1-py3-none-any.whl |
|---|---|
| Size | 340.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba90c97572650c55c8d61826554da0195b7c49edd8ec29ffe0e309f92724bdfe
|
|
BLAKE2b-256 checksum How to use checksums |
f74d4fcd46c333f15782ef2dae949568a0e96980edf1ada72640b43695ee1f05
|
| 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 21, 2026.
Transparency logSecurity for gcl-sdk 3.7.1
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 gcl_sdk-3.7.1.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 21, 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.
