Skip to main content
This is the audited first-party package catalog for the public OpenCLIs estate. The 2026-07-21 snapshot contains 48 installed first-party packages. That is not the same count as raw files in ~/.openclis/bin, source initiate/ directories, Cargo binary targets, or documentation pages: wrappers, backups, internal helpers, multi-binary packages, and suite pages make those surfaces legitimately differ. Each row below maps one package identity to exactly one public documentation owner. Run openclis list --json for local install state and the package’s own --version plus public CDN latest.json for release agreement. The 2026-07-16 registry repair closes a second, independently checked surface: all 48 installed first-party package names now have a public api.openclis.com/tool/<name> row. All 48 source manifests use this catalog’s owning pages as canonical docs_url values, working homepages, and explicit ai_use and pairs_with relationships. Private repositories remain identified by the registry repo field, but do not advertise a public source_url that would resolve to a 404.

Platform, OS, Web, and Security

Terminal, Runtime, Sessions, and Protection

Code Intelligence, Knowledge, and Evaluation

Ingestion and Conversion

Usage and Cost Suite

Known Release Identity Exceptions

These are public facts, not documentation gaps:
  • monolex-cli: registry metadata says 0.2.1 and names a newer build than the CDN artifact path; the exact published payload self-identifies as 0.2.0.
  • monolex-monometer-daemon: public package is 0.3.5; the development runtime observed during the audit reports source-ahead 0.4.5.
Each owning page documents the affected payload’s exact command surface. Fixing a release identity mismatch requires a new release or metadata repair; rewriting the docs to pretend the layers agree would erase the evidence.