AIPM
Theme

Roadmap

See what AIPM is building next.

AIPM is moving from a working registry to a dependable product. This roadmap shows what works now, what needs more polish, and what should wait until the core workflow is stable.

Start using AIPMPublish a skill

Available now

  • Public registry website with package search and package detail pages.
  • CLI install flow for AI skills and tool files.
  • Publisher accounts, org namespaces, package reservations, and short-lived publish tokens.
  • CLI publishing with init, import, add, status, preview, validate, and push steps.
  • Public docs for security, privacy, terms, status, FAQ, best practices, and discoverability.

Near term reliability

  • Production checks for HTTPS, security headers, health, readiness, search, install, and blocked unauthenticated publishing.
  • Better consistency, rollback, backup, and restore for publishing.
  • More CLI commands such as update, remove, verify, clean, and pack.
  • Clearer dashboard messages for failed publishes, package versions, and token expiry.

Trust and registry depth

  • Package abuse reports, takedowns, appeals, and owner transfer.
  • Verified publisher labels and clearer package origin.
  • Server-side package scanning, risk levels, and stricter install options.
  • Private packages and organization-level access controls.
  • More package types beyond skills, including rules, MCP bundles, and environment bundles.

Platform expansion

  • More adapters for AI tools and editors beyond Cursor, Claude, and Codex workflows.
  • Dependency resolution, lockfiles, conflict detection, and offline reinstall from local cache.
  • AIPM MCP server so agents can find and install missing skills during work.
  • Desktop app and enterprise registry options after the CLI and hosted registry are stable.

How to read this roadmap

Items are ordered by what the product needs first. AIPM should make install, publish, recovery, and trust reliable before adding larger platform features.