Software ecosystem
Porting status
Porting status should answer whether a named component builds, runs and passes relevant tests on a specific architecture, ABI, OS and release.
What you’ll find
Porting status should answer whether a named component builds, runs and passes relevant tests on a specific architecture, ABI, OS and release. It should also identify patches, unsupported features and the maintainer responsible for keeping the result current.
Choose the right route
1. Levels
Separate unknown, investigated, builds, runs basic tests, passes upstream tests, integrated and maintained.
2. Context
Record target, release, toolchain, configuration, test count, last verification and links to patches or issues.
3. Ownership
Name upstream and CHERI-side maintainers, review cadence and criteria for declaring support.
How to use this page
Transparent status lets adopters find blockers and avoid repeating work or overestimating ecosystem readiness.
Check before relying on an item
Repository activity or a successful one-off build is not the same as maintained support. Avoid undated green status labels.
Treat build, test, integration, upstream and maintained support as distinct states. Name the target and last verified date.