APM: dependency manager for AI agents
APM is an open-source, community-driven dependency manager for AI agents.
Verified
Core facts
Read by a script from the official API, not rewritten by a model.
- Repository
- https://github.com/microsoft/apm
- License
- MIT
- Languages
- Python
- Maintainer
- microsoft
- Homepage
- https://microsoft.github.io/apm/
- Verified
What it is
APM is an open-source, community-driven dependency manager for AI agents. With it, a project's agentic dependencies are declared once in apm.yml. AI coding agents need context to be useful, such as standards, prompts, skills and plugins. The project's tagline is "Portable by manifest. Secure by default. Governed by policy."
Main features
Packages can depend on packages, and APM resolves the full tree.
APM builds Copilot, Claude, and Cursor plugins with dependency management, then exports standard plugin.json.
APM marketplaces install plugins from curated registries in one command.
The apm pack command bundles configuration as a zipped package or a standalone plugin.
APM provides a GitHub Action for automated workflows.
An APM manifest, declared once, is deployed across Copilot, Claude, Grok Build, Cursor, OpenCode, Codex, Gemini, Windsurf and Kiro.
Getting started
APM publishes native release binaries for macOS, Linux, and Windows x86_64.
When APM is installed with Homebrew, Homebrew manages installation and updates, and no custom tap is required.
For standalone installations, apm self-update reuses the matching platform installer.
Other install methods are pip, WinGet, and Scoop.
APM can also add an MCP server, wired into Copilot, Claude, Cursor, Codex, OpenCode, Gemini, Windsurf, and Kiro.
Who it is for
You do not need Homebrew to use APM. Agent context is executable in effect, since a prompt is a program for an LLM. Every install scans for hidden Unicode that can hijack agent behavior.
The apm install command blocks compromised packages before agents read them. The apm audit command runs the same checks on demand. The lockfile pins integrity hashes.
The apm.lock.yaml file pins the resolved tree. Transitive MCP servers are gated by trust prompts. Transitive MCP servers require explicit consent.
The apm audit command rebuilds agent context in scratch and diffs it against the working tree to catch hand-edits before they ship. SBOM export emits a standard inventory of what reached disk, straight from the lockfile; it is provenance for procurement, not a compliance attestation. The apm-policy.yml file governs what gets installed, while the agent harness governs what runs.
The two planes do not overlap.
Sources
This page is written from the official sources below. Open them to check the original text.
- GitHub READMEhttps://github.com/microsoft/apmFetched
Verified ·
This page is written by AI from the official sources above and checked automatically. This site has not tested it. Found a mistake? Tell us.