Inspiration
Installing software should be simple, regardless of the operating system. Siorb lets users request an app by name and safely uses the native package manager available on Windows, macOS, or Linux. But user is no longer obliged to remember package manager name in specific sys op
What it does
Siorb is a cross-platform CLI for discovering, installing, updating, and removing software. It detects the system and package manager, resolves human-friendly names to verified native package IDs, and presents an execution plan before making changes.
It supports search, diagnostics, dry-runs, JSON output, and portable bundles—without accounts, servers, or API keys.
How we built it
Siorb is built in Rust as a platform-neutral core with adapters for individual package ecosystems. Commands are executed through safe argument arrays rather than shell interpolation.
Package metadata, documentation, and the website are static. Automated workflows validate changes and prepare releases.
Challenges
The same application can have different identifiers, publishers, versions, scopes, and installation rules across platforms. Package managers also vary in privileges, update behavior, prompts, and rollback support.
Security is critical: incorrect mappings can lead to incorrect software being installed. Siorb therefore focuses on exact IDs, validated metadata, visible plans, and native trusted sources.
Accomplishments
Siorb provides one consistent interface while preserving the strengths of each operating system’s native package ecosystem.
It avoids fuzzy installs, hidden privilege escalation, shell-command injection, and misleading rollback promises.
What we learned
A universal package tool should not replace every dependency solver. Its role is to understand user intent, select a safe native path, preserve software identity, and clearly explain the result.
Reliable package metadata and continuous verification are the core long-term challenge.
What’s next
The initial MVP targets Windows, macOS, and Ubuntu with support for major native package managers and a curated application registry.
Future work includes signed registry data, self-updates, bundle restore, package verification, more Linux backends, offline support, SBOM export, organization policies, and community-maintained mappings.
Log in or sign up for Devpost to join the conversation.