Inspect before install.
omapkg cannot prove that arbitrary upstream software is harmless. It ties the request, source, generated recipe, build, signature, and release decision together.
Source and agent boundary
Users submit names and upstream URLs. They do not submit executable PKGBUILDs. The factory reads upstream files and submitted downloads as hostile data, has only allowlisted tools, and receives no signing keys, OAuth secrets, worker credentials, or production write access.
Build boundary
An online verification pass resolves redirects, immutable refs, checksums, licenses, dependencies, and download metadata. The factory generates a recipe from the reviewed input. After review, a controlled extractor handles supported package inputs inside the isolated offline worker; network access stays disabled while it extracts and builds. The worker uploads an attestation and artifact, then the system removes the disposable environment.
Signing and release
A separate signing service checks the reviewed revision, manifest, worker lease, attestation, and tests before signing a binary. Every successful build enters dev. A maintainer promotes a dependency-compatible batch to stable after the published gates pass.
Public data boundary
Public package pages show approved source, license, architecture, checksums, signatures, SBOMs, attestations, tests, and channel history. Internal prompts, private credentials, worker details, and unredacted logs stay restricted.