# Omni Line Omni Line is a self-hosted package registry for teams that publish and consume packages across multiple ecosystems. It provides hosted, proxy, and virtual registries through one UI and REST API, with organization access controls and OSV-backed vulnerability checks. - Findings24: - Website: - Pricing: Freemium - Categories: Developer Tools ## What is Omni Line? Omni Line is a self-hosted package registry for npm, Composer, Docker, PyPI, Go, Cargo, Maven, RubyGems, Conan, and Multipurpose packages. It gives teams one web interface and REST API for creating registries, managing packages, issuing tokens, and configuring access while keeping artifacts and metadata on infrastructure they operate. The product supports three registry modes: hosted registries for private packages, proxy registries that cache an upstream registry, and virtual registries that aggregate member registries behind one endpoint according to priority. Developers can continue using familiar package clients such as npm, pip, Docker, and Composer, while personal access tokens authenticate command-line and CI workflows. Omni Line checks stored package versions against the public OSV database. Scans can run manually, on a schedule, or in the background when hosted versions are published. Results appear in a registry Vulnerabilities tab and on package-version badges; teams can record mitigation notes and fixed versions. Per-registry install protection can deny versions with open malware advisories or advisories at configured severity levels, although Docker image-layer scanning and Multipurpose artifact scanning are not available. The software is commercial and self-hosted. Pro includes all features, unlimited deployments for one company, OIDC SSO, organization RBAC, scoped personal access tokens, filesystem or S3-compatible storage, and installation options including Docker Compose, Helm, Ansible, and cloud templates for AWS, Azure, and DigitalOcean. A free 30-day trial is available; the listed Pro price is $2,499 per year, with renewals at $2,249 per year. ## What can Omni Line do? ### Multi-ecosystem registry surface Supports npm, Composer, Docker, PyPI, Go, Cargo, Maven, RubyGems, Conan, and Multipurpose packages behind one UI and API. ### Hosted, proxy, and virtual modes Store private packages, cache an upstream registry, or aggregate registries behind one prioritized endpoint. ### Familiar client and CI workflows Existing package clients can point to the Omni Line URL, while scoped personal access tokens authenticate publishes and installs. ### OSV vulnerability scanning Match package names and versions against the public OSV database through manual, scheduled, or on-publish background scans. ### Install-time supply-chain controls Optionally block versions with open malware advisories or advisories at or above a configured severity threshold. ### Team administration and deployment options Use organization RBAC, OIDC SSO, filesystem or S3-compatible storage, and Docker Compose, Helm, Ansible, or supported cloud installation templates. ## Use Cases ### Centralize private package publishing Product and platform teams can host internal packages for several languages without maintaining a separate registry interface for each ecosystem. ### Keep public dependencies available Teams can place a proxy registry in front of an upstream source to cache packages and reduce dependence on upstream availability or rate limits. ### Simplify client configuration A virtual registry can combine member registries behind one URL, allowing developers and CI systems to use a single endpoint while Omni Line applies registry priority. ### Review dependency risk at the registry Platform or security teams can scan packages already stored or proxied into the registry, review advisories, document fixes, and optionally prevent risky versions from reaching CI or developer machines. ## Frequently Asked Questions ### Can Omni Line run on a company’s own infrastructure? Yes. It is self-hosted by design. Artifacts use a pluggable storage driver, with local disk as the default and S3-compatible object storage available, while metadata is stored in PostgreSQL. ### What is the difference between hosted, proxy, and virtual registries? Hosted registries store private packages, proxy registries cache an upstream registry, and virtual registries aggregate member registries behind one endpoint according to priority. ### How do developers and CI systems authenticate? The web UI uses standard login sessions. Command-line tools and CI systems use scoped personal access tokens. Registries can also allow anonymous reads when public access is required. ### What does vulnerability scanning cover? Omni Line queries the public OSV API for matching package names and versions. Docker image-layer scanning and Multipurpose artifact scanning are not currently available, and the server needs outbound HTTPS access to api.osv.dev. ### Is there a trial and how is the product licensed? A free 30-day trial includes every feature and is activated with a license key in the self-hosted instance. Omni Line is proprietary commercial software; Pro is licensed at $2,499 per year for one company, with unlimited deployments and no per-seat pricing. ## Quick Facts - **Product type**: Self-hosted package registry - **Supported package types**: npm, Composer, Docker, PyPI, Go, Cargo, Maven, RubyGems, Conan, and Multipurpose - **Registry modes**: Hosted, proxy, and virtual - **Security data source**: Public OSV database - **Deployment**: Customer-operated infrastructure; Docker Compose, Helm, Ansible, and supported cloud templates - **License model**: Commercial self-hosted license with a 30-day trial