OpenA2A AIM (Agent Identity Management) at one year

The first commit of OpenA2A AIM (Agent Identity Management) was made on October 24, 2025, with the message feat: initial release of AIM (Agent Identity Management). See the first commit.

AIM is an open-source platform, licensed under Apache-2.0, that gives AI agents an identity. An agent registers with the capabilities it declares, the SDK has AIM authorize each action the agent takes, and AIM records the action in an audit log. A request for a capability the agent did not declare is recorded as a violation, and refused when the organization's security policy blocks it. We introduced it on this blog on December 16, 2025.

What you can run today

The current platform release is AIM platform 1.0.0, published on June 1, 2026. It ships the API server and the dashboard as signed container images for linux/amd64 and linux/arm64 on GHCR and Docker Hub, with SBOMs attached to the release, and a quickstart script that runs the API server, the dashboard, PostgreSQL and Redis on one machine with Docker Compose.

Read the security notice on the 1.0.0 release page before you run its dashboard image. That image bundles a Next.js version affected by a critical advisory (GHSA-rqgr-f9m6-xphr), and the notice names the replacement image, pinned by digest. Fixed vulnerabilities in AIM are published as security advisories on the repository.

SDK versions

As listed on PyPI and npm on October 12, 2026:

• Python: aim-sdk 2.0.3, released September 9, 2026. Install with pip install aim-sdk.
• TypeScript: @opena2a/aim-sdk 1.3.1, released September 2, 2026. Install with npm install @opena2a/aim-sdk.

Each SDK works with an AIM server and an SDK token from that server; on its own it protects nothing. The quick start walks through registering an agent and protecting an action with a capability grant.

Since aim-sdk 2.0.0, an action that AIM denies raises an error and does not run, in every enforcement mode. Since @opena2a/aim-sdk 1.2.0, the TypeScript SDK's runtime-protection telemetry stays off until you turn it on. The Java SDK is built from source, as its README describes; publishing it to Maven Central is under consideration on the roadmap.

What comes next

AIM has published no platform release since 1.0.0. The changes merged since then are listed under Unreleased in the changelog, and the roadmap lists publishing them in a versioned platform release as planned work.

The roadmap sorts work into four classes. A Shipped line names the release it shipped in and when. In progress means a pull request is open, or merged and not yet released. Planned is intended work with no open pull request, whose scope and order may change. Under consideration is not scheduled. Only Shipped lines carry versions and dates.

In the roadmap as updated on October 10, 2026, the work in progress is the agent page in the dashboard showing why a call was refused and where an administrator grants the missing capability. Under consideration are, among others, multi-factor sign-in for dashboard accounts, custom roles with fine-grained permissions, and an interactive API reference generated from an OpenAPI description of the REST API.

How to follow and take part

Watch the releases: each release page lists the changes in that version. Open an issue to request a capability or report a bug. Report a vulnerability as described in the security policy, not in a public issue.