Fred Core
fred-core is the shared utility layer for Fred backends. It centralizes the
foundational building blocks that must stay consistent across services.
What it provides
- Configuration helpers used by multiple backends.
- Storage and session primitives.
- Security and access-control utilities (ReBAC helpers, Keycloak helpers).
- Common runtime helpers (logging, KPI, scheduling utilities).
- The pod floor — configuration files, identity, contributed-name rules — now
lives in
fred-podand is re-exported from here, so existingfred_coreimports are unchanged.
What it is not
- A full runtime or service on its own.
- A public SDK for agent authoring (that is
fred-sdk).
Install
pip install fred-core
Notes
fred-core is designed for internal Fred services and adapters. If you are
building agents or workflows, you likely want fred-sdk instead. In most
cases, end users should not install fred-core directly: fred-sdk[agents]
pulls it in. A Knowledge Base pod wants fred-pod (via the lean fred-sdk
base) and not this package at all.
Development validation
make testruns the default offline test suite.make coverage-offlineruns the canonical offline coverage command with terminal missing-line output.
2 maintainers
Metadata
2 maintainers
Release files for fred-core 4.5.5
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 | |
|---|---|---|---|---|
| fred_core-4.5.5.tar.gz | 484.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fred_core-4.5.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / fred_core-4.5.5.tar.gz
| Download URL | fred_core-4.5.5.tar.gz |
|---|---|
| Size | 484.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20aa1f2e3b70819769b410ef4fd83d6038d76b855af3dc18d9f1a1b8fb464135
|
|
BLAKE2b-256 checksum How to use checksums |
ba2bef4d0c4af767404137eab697b68edf55fcfe3c57a3bedefde3ea5183c9b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / fred_core-4.5.5-py3-none-any.whl
| Download URL | fred_core-4.5.5-py3-none-any.whl |
|---|---|
| Size | 680.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63936e4d59cfa735a3ccf713d9f7860d2098a4c5eb4cc590ae261f2ad93f9822
|
|
BLAKE2b-256 checksum How to use checksums |
ed8dc856f3e223bdab555b6e1533d0301c6d88f0edbe3bb1f5b71dbbac1a267d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for fred-core 4.5.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
