omnibase_core
ONEX Core Framework - Base classes and essential implementations
Decision gist · record as of 2026-08-14
Yes, if you are building or consuming ONEX nodes or need a contract-driven, event-driven node execution framework. The package is actively maintained, has low install friction, and carries no known vulnerabilities. Requires Python 3.12+. Beta status means the API may evolve, so pin versions carefully in production. Not necessary if you do not need node-based workflow architecture.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.12 or later.
- Low friction; pure Python wheel with 13 runtime dependencies.
- Active maintenance—last commit 2026-08-14, released 2026-08-01.
License · maintenance · safety
MIT (permissive) — MIT permissive license; no restrictions on commercial or proprietary use.
last release 2026-08-01 (13 days) · last repo commit 2026-08-14 · 7 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 160,076 downloads/mo, #10,674 on PyPI
Alternatives
Verify before relying
pip install omnibase_core
from omnibase_core.nodes import NodeCompute
class NodeMyFeature(NodeCompute):
pass- Whether the 13 runtime dependencies (blake3, cryptography, tree-sitter, etc.) introduce any transitive security concerns beyond the package itself.
- Stability guarantees or API compatibility policy for a Beta-status framework.
- Performance characteristics or scalability limits for large node graphs or high-throughput workflows.
What it is and what it does
omnibase_core is the kernel of the ONEX platform, a contract-driven node execution framework for building event-driven workflows. It provides four core node archetypes—EFFECT, COMPUTE, REDUCER, and ORCHESTRATOR—along with base classes, contract models, validation tooling, and dependency injection patterns. The framework is designed so that YAML contracts declare inputs, outputs, capabilities, and lifecycle constraints, with custom Python behavior added only when the contract cannot express the behavior.
The package owns node execution vocabulary, handler contracts, event envelopes, error models, and validation entrypoints. It is intended for teams building contract-driven nodes, extending validation or runtime internals, or consuming core types and architecture vocabulary from downstream packages. The framework explicitly does not own concrete infrastructure clients, protocol-only service interfaces, compatibility shims, or portable workflow packages—those live in separate repos (omnibase_infra, omnibase_spi, omnibase_compat, omnimarket).
Use it for
- Build a contract-driven COMPUTE, EFFECT, REDUCER, or ORCHESTRATOR node by subclassing the appropriate base class and declaring inputs/outputs in YAML.
- Validate node contracts, topics, and documentation links using CLI entrypoints like onex-validate-links and onex-validate-topics.
- Consume core ONEX types, error models, and validation tools from downstream packages that need canonical architecture truth.
- Extend validation, contract handling, or node execution internals for a custom ONEX runtime implementation.
- Scaffold and develop new nodes with dependency injection and event-driven patterns following ONEX conventions.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building or consuming ONEX nodes or need a contract-driven, event-driven node execution framework.
The package is actively maintained, has low install friction, and carries no known vulnerabilities. Requires Python 3.12+. Beta status means the API may evolve, so pin versions carefully in production. Not necessary if you do not need node-based workflow architecture.
Install
omnibase-core on PyPI
Before you install
Low friction; pure Python wheel with 13 runtime dependencies. Active maintenance—last commit 2026-08-14, released 2026-08-01. Requires Python 3.12+.
Requires Python 3.12 or later.
License in practice
MIT permissive license; no restrictions on commercial or proprietary use.
Quickstart
pip install omnibase_core
from omnibase_core.nodes import NodeCompute
class NodeMyFeature(NodeCompute):
passVerify before relying
- Whether the 13 runtime dependencies (blake3, cryptography, tree-sitter, etc.) introduce any transitive security concerns beyond the package itself.
- Stability guarantees or API compatibility policy for a Beta-status framework.
- Performance characteristics or scalability limits for large node graphs or high-throughput workflows.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.12 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 13 packagesblake3clickcryptographydeepdiffdependency-injectorhttpxjsonschemapathspecpydanticpyyamlruamel-yamltree-sitter-pythontree-sitter |
| Maintenance | Actively maintained 13 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 160,076 / month, #10,674 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaIntended Audience :: DevelopersProgramming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.12Topic :: Software Development :: Libraries :: Application FrameworksTopic :: Software Development :: Libraries :: Python ModulesTyping :: Typed |
Evidence: omnibase_core-0.46.8-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “node execution framework”
- omnibase_coreomnibase_core provides the ONEX platform kernel: base classes,…
- ClusterShellClusterShell is a Python framework for running commands in parallel…
- kenbunKenbun statically discovers and analyzes applications in Python and…
Give your agent the search over MCP, or paste the wish link into any chat.
More Python Modules packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
PyYAML parses and emits YAML 1.1 data format, enabling serialization and deserialization of configuration files and Python objects to and from human-readable YAML text.
Pydantic validates Python data structures against type hints, coercing and checking input at runtime to ensure it matches a declared schema.
Provides reusable metadata objects for use with PEP-593 `typing.Annotated` to express common constraints like bounds, collection sizes, and predicates on types.
Install it if you use or build libraries that need to express type constraints in a standardized, inspectable way—or if you want to annotate your own types with…
Provides runtime tools to inspect and introspect Python type annotations, enabling programmatic examination of type hints at execution time.
See also omnibase-compat · omnibase_spi · cloudshell-core · dcc-mcp-core · autogen-core · apimatic-core-interfaces · arcade-core · openbb-core · uipath-runtime · spec-kitty-tracker