Surface A · binaries
signedomarpkg hosts packages whose license permits redistribution. Each release points to its source digest, build inputs, attestation, signature, and test evidence.
Omarchy Package Repository
Packages you can inspect.
omarpkg turns a package request into a generated, reviewed, and traceable Arch build. The source stays visible. The signing key stays away from workers.
- 01 Package request
Name and upstream URL.
- 02 Maintainer approval
Area queue and security sign-off.
- 03 Factory
An agent generates the PKGBUILD.
- 04 Human review
A maintainer approves the generated diff.
- 05 Build and signing
Verified sources, an offline build, separate signing.
- 06 Dev channel
Quarantine, smoke tests, and feedback.
- 07 Stable channel
A maintainer promotes a compatible batch.
- 08 Distribution
Signed packages, recipes, and evidence.
0stable releases
0in dev
0open requests
Public catalogue
View all packagesLatest releases
No packages published yet.
The catalogue will show releases after a reviewed build reaches dev or stable. You can still request a package.
Request a packageTwo distribution surfaces
Build records.
Redistributable software becomes a signed binary. Software we cannot redistribute remains a recipe that fetches vendor bytes with a pinned checksum.
Surface B · recipes
vendor fetchChrome, NVIDIA, Zoom, Spotify, and similar packages keep their bytes at the vendor. omarpkg publishes the reviewed recipe and pinned checksum.
Stable channel.
We cannot promise every package works perfectly. Package inputs, review decisions, build evidence, and signatures are visible. The pipeline is designed to prevent packages from attacking users.