Core
BusyBox/fallbacks, certificates, SSH, archives, basic build tools and shared libraries.
Packages
Packages are published only after a successful build and smoke test.
The public index should show confirmed recipes only. Broken entries, local overrides and experiments stay outside the default release.
Native build
make, cmake, ninja, pkg-config, Python, Node.js and tools needed for the compile flow.
AI base
Target set: git, HTTP client, jq, less, editor and diagnostics after dependency staging is fixed.
Current status
Starter package status without hiding blockers.
| Group | Status | Notes |
|---|---|---|
| Confirmed foundation | confirmed set | The backend currently reports 42 packages/recipes in the database and 12 confirmed packages, including build tools, certificates, SSH and core libraries. |
| Dependency staging | blocker | git, curl, rsync and nano wait for stable dependency visibility in the PC builder. |
| Runtime aliases | needs work | coreutils, grep and gzip should not go to v1 until runtime file operations are confirmed. |
| Package queue | active plan | Order: confirm wget, jq, less, then curl/git/nano/rsync after staging fix. |