npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentxm/extension-resolution

v0.30.2

Published

AXM extension resolution policy: what a configured or requested extension resolves to and whether that resolution may be accepted — release-age policy, version selection, configured-entry and Pack dependency resolution, workspace source authority, publish

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

craigsmithamcraigsmitham

Keywords

Readme

@agentxm/extension-resolution

Extension resolution policy for the AXM client: what a configured or requested extension resolves to, and whether that resolution may be accepted.

  • Minimum release age — parseMinimumReleaseAge, isVersionEntryEligibleAt, releaseAgeEvidence, exemption and holdback records, and the operator's per-invocation ReleaseAgePosture.
  • Version selection under that policy — resolveVersionEntryWithReleaseAge, resolveVersionEntryForReleaseAge, and the named Registry target decisions decideNamedRegistryVersion and namedRegistryCandidates.
  • Configured-entry resolution — resolveConfiguredSkill and its six siblings, resolveConfiguredRegistryEntry, and the ResolvedConfiguredEntry vocabulary the lockfile and plans carry.
  • Pack dependency resolution — resolvePackDependencies, resolvePackDependenciesWithReleaseAge, the resolved-dependency map schema, and acceptedPackDependencyResolver for deterministic recovery.
  • Source authority — evaluateSourceAuthority: whether a requested source may replace the configured one for the same target.
  • Publisher-binding trust — classifyPublisherBindingTransition and the proposal vocabulary. Shaping the resulting plan risk condition belongs to the feature that owns the plan, not here.
  • Official AXM skill inspection — evaluateAxmSkillCandidate and readAxmSkillWorkspaceCompatibility currently obtain candidate facts and invoke the compatibility policy owned by @agentxm/cli-maintenance.

Exports . and ./live.

Dependency budget: @agentxm/extension-model, @agentxm/registry-protocol, @agentxm/extension-content, @agentxm/extension-sources, and @agentxm/workspace-state, and the published official-skill APIs of @agentxm/cli-maintenance. Deciding what a configured entry resolves to needs workspace facts and source acquisition, so this package sits above @agentxm/workspace-state: state must never depend on it.

Provider contract

@agentxm/extension-sources (an integration) fetches the Registry index, maps entries to refs, and probes archives, but it may not import this core package. It therefore declares ports whose vocabulary lives in @agentxm/extension-model/unstable/sources/source-host-provider:

  • RegistryResolutionPolicy — implemented structurally by this package's decision functions and bound by the application composition root (apps/cli/src/cli-runtime/registry-resolution-policy-live.ts).
  • AxmSkillCandidateGate — implemented by AxmSkillCandidateGateLive in this package's ./live.
  • WorkspaceCatalog — implemented by @agentxm/workspace-projection, which owns the agent-selection facts the catalog reports.

Shared release selection (selectVersion, resolveVersionEntry: exact requests, yank handling, and range maxima) belongs to @agentxm/extension-model/unstable/version-constraints/version-selection. It consumes domain release facts and preserves the selected candidate. Registry clients and this package use it without making wire schemas own the algorithm; release-age and other client admission policies remain here.

Official-skill compatibility and recovery are owned by @agentxm/cli-maintenance, with separate domain, application, and composition entry points. They are absent from this package's public exports. Registry candidate probing and workspace inspection still require a further acquisition/application separation; the policy extraction does not make the current provider port design the target architecture.

Unstable and unsupported — use the axm.sh CLI.

FSL-1.1-MIT © 2025-2026 AgentXM, Inc.