# Install orogene with Homebrew, zypper node_modules/ package manager and utility toolkit. Version 0.3.34 via Homebrew; verified 2026-07-11. Also installable with zypper: sudo zypper install oro. ## Install ```sh sudo av install brew:orogene ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install orogene ``` Evidence: local Homebrew formula metadata ### Linux - zypper (92%): ```sh sudo zypper install oro ``` Evidence: openSUSE Tumbleweed package metadata: oro from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Package facts - **Package key:** brew:orogene - **Package manager:** Homebrew - **Version:** 0.3.34 - **Source summary:** node_modules/ package manager and utility toolkit - **Homepage:** - **Repository:** - **Last updated:** 2026-07-11T09:50:50+09:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - oro (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.3.34 ## Project history and usage Orogene is a Rust-oriented package manager for JavaScript projects that need a maintained node_modules tree. Its own tagline, "Makes node_modules happen," is literal: the tool is aimed at bundlers, CLIs, and Node.js applications where dependency installation speed, cache reuse, and reproducible local trees matter. ### Project history GitHub records the orogene/orogene repository as created on 2020-07-14. Public releases in 2023 shipped prebuilt binaries, installer scripts, npm packaging, and crates.io distribution, showing a project that tried to meet JavaScript developers where they already install tools while implementing the installer in Rust. The README later documented a shift to a closed-source development model with paid licenses, with releases hosted from the GitHub repository and limited features without a developer license. That makes Orogene an unusual entry in the Node package-manager space: a performance-focused package manager whose public history includes both open-source Rust experimentation and a sustainability/licensing pivot. ### Adoption history Orogene has distribution hooks through GitHub releases, npm, crates.io, Homebrew, and distro packaging metadata, but the available public sources do not show broad ecosystem adoption comparable to npm, Yarn, or pnpm. Its adoption story is better described as niche package-manager experimentation and benchmarking interest than as a default JavaScript workflow. ### How it is used Developers use the oro executable to make or refresh node_modules for projects and tools that expect Node's traditional dependency layout. The README emphasizes speed, low memory use, low disk use, and integration into workflows where developers do not want to think about whether node_modules matches dependency metadata. ### Why package nerds care For package nerds, Orogene is interesting because it attacks the old node_modules installation problem with a Rust implementation and an explicit performance agenda. It also illustrates the business tension around package tooling: even infrastructure-flavored developer tools can move from open development to paid licensing when maintenance cost becomes part of the design. ### Timeline - 2020-07-14: GitHub repository created. - 2023-05-21: release v0.3.27 published with prebuilt binaries, installer scripts, and npm package artifacts. - 2023-10-09: release v0.3.34 published, one of the visible public releases before the repository's later closed-source-development notice. ### Related projects - Orogene belongs to the same problem family as npm, Yarn, and pnpm: all manage JavaScript dependencies, but Orogene focuses its public identity on making node_modules fast and low-fuss rather than replacing the Node package ecosystem itself. ### Sources - - - - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ./oro.kdl ## Credential files - Unix: ./oro.kdl ## Other Package-Manager Records - zypper - oro - 2.0.8-298.7: installed executable or alias match | openSUSE Tumbleweed package metadata: oro from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Full regular expressions API | https://jakarta.apache.org/oro/ - zypper - oro-javadoc - 2.0.8-298.7: installed executable or alias match | openSUSE Tumbleweed package metadata: oro-javadoc from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Javadoc for oro | https://jakarta.apache.org/oro/ ## Combined YAML source View the package source record on GitHub. [combined/orogene.yml](https://github.com/mxcl/pkgdb/blob/main/combined/orogene.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph