omnibase_core

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

omnibase_core provides the ONEX platform kernel: base classes, contracts, validation tools, and core architecture vocabulary for building and executing node-based workflows with dependency injection and event-driven patterns.

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

pip install omnibase-core

uv add omnibase-core

poetry add omnibase-core

Installing omnibase_core

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+.

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):
    pass

Requires Python 3.12 or later.

Verify 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

Evidence: omnibase_core-0.46.8-py3-none-any.whl

Keywords: architecture, base-classes, dependency-injection, error-handling, event-driven, framework, infrastructure, node-architecture, onex

Tags

More Python Modules packages