--- id: omnibase-compat version: "0.5.6" license: unclear license_treatment: unclear maintenance: active --- # omnibase-compat — Thin shared structural package for cross-repo enums, wire DTOs, event envelopes, primitives, and experimental schemas. License: unclear · Maintenance: active · Downloads: 103.2K/mo ## What it is and what it does omnibase_compat is a structural compatibility layer designed for multi-repository systems that need to share enums, data transfer objects, event models, and concurrency primitives without creating circular dependencies through core or infrastructure packages. It explicitly avoids importing from omnibase_core, omnibase_spi, or omnibase_infra at runtime, enforced by CI validation. The package is used by repositories like dashboard, intelligence, memory, market, and governance to exchange event envelopes, status enums, routing DTOs, and migration shims. It includes experimental artifact tracking with lifecycle metadata (ticket and review milestone) and provenance-tracked enum copies from upstream sources. Runtime dependencies are minimal: only pydantic and typing-extensions. Use it for: - Share event envelope schemas across OmniNode repositories without creating import cycles. - Define canonical enum copies with explicit source provenance for use by multiple domain repos. - Transport wire DTOs and routing models between dashboard, intelligence, memory, and market services. - Provide temporary migration shims with explicit removal dates and target migration paths. - Implement concurrency and environment primitives that do not depend on OmniNode runtime packages. ## Worth the install? AI-flagged interpretation of the facts above — verify before relying. Provides shared structural types—enums, DTOs, event envelopes, and concurrency helpers—for cross-repository communication within an OmniNode ecosystem without creating import cycles. Yes, if you are part of the OmniNode ecosystem and need to share structural types across repositories without circular dependencies. The low install friction, active maintenance, and zero known vulnerabilities support adoption. However, verify the license status first—the metadata shows no SPDX identifier, which may be a blocker for some projects. If you are outside the OmniNode ecosystem, this package is likely not applicable. ## Install pip install omnibase-compat uv add omnibase-compat poetry add omnibase-compat ## Installing omnibase-compat Before you install: Low install friction: pure Python wheel with only pydantic and typing-extensions as runtime dependencies. Actively maintained with a release 35 days ago. License in practice: License treatment is unclear; no SPDX identifier or raw license text is available in the package metadata. Verify the actual license before using in proprietary or restricted contexts. Quickstart: pip install omnibase-compat from omnibase_compat.enums.enum_message_category import EnumMessageCategory from omnibase_compat.models.event_envelope import EventEnvelopeV1Minimal Requires Python 3.12 or later. Verify before relying: - Whether the license is open-source or proprietary; metadata shows no SPDX identifier. - Whether this package is intended for use outside the OmniNode ecosystem or is internal-only. - Stability guarantees for the structural types and whether breaking changes are expected. ## Package facts - License: not declared (unclear) - Python support: supports_current - Install friction: low - Maintenance: active - Downloads: 103.2K/month (top 15,000 on PyPI) - Known vulnerabilities: none known ## Tags shared data types across repos, cross-repository enums and DTOs, event envelope models, wire protocol structures, dependency-free structural types, compatibility layer for microservices, omninode shared schemas, omninode-ecosystem, data-models, cross-repo-sharing [View on SkillFed](https://skillfed.io/packages/omnibase-compat) · [View on PyPI](https://pypi.org/project/omnibase-compat/)