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

@indx-workspace/platforms

v0.6.9

Published

The PlatformTarget port, the per-field verdict model and the conformance kit that every agent-platform translator (Copilot Studio, Foundry, Gemini Enterprise, AgentCore, ...) is built on; pure, no I/O.

Readme

@indx-workspace/platforms

Translators from a PortableProject (@indx-workspace/contracts/portable-agent) to the files an external agent host takes, and back where the host allows it. The design is ADR-0133 D6-D8. The package is published in lock-step with @indx-workspace/contracts; six targets ship: claude-managed-agents, copilot-studio, m365-declarative-agent, microsoft-foundry, gemini-enterprise (compile only) and aws-agentcore, each at @indx-workspace/platforms/<target>.

  • PlatformTarget is the port: an id, a capability matrix, an options schema, a pure compile and an optional import.
  • Every field of the project gets one verdict in the report: native, mapped, or dropped with a drop code. Nothing is dropped silently. Paths are toolEndpoint, then <agent>.<field> (portableFieldPaths).
  • Call compileForPlatform(target, project, options), not target.compile: it checks the root agent, validates the options and orders the output.
  • Production code is pure: no Node built-in, clock, randomness or environment. platforms-are-pure in dependency-cruiser.config.mjs and an ESLint block enforce it. The only npm dependencies are @indx-workspace/contracts, zod and yaml (src/dependencies.test.ts), and the package tsconfig.json has no Node types; tsconfig.test.json adds them for the kit and the tests.

Adding a target

  1. Add src/targets/<id>/index.ts exporting a PlatformTarget whose id is in PLATFORM_IDS, add it to PLATFORM_TARGETS in src/registry.ts (in PLATFORM_IDS order) and give it a ./<id> subpath in package.json exports and publishConfig.exports.
  2. Build its report from portableFieldPaths, capabilityOfPath and the native, mapped and dropped builders.
  3. Test it with @indx-workspace/platforms/testing: runPlatformConformance(target) and a golden from expectGoldenFiles (data files) or expectGoldenBundle (generated source, one .txt). UPDATE_GOLDEN=1 rewrites goldens. loadGoldenProject reads <goldenDir>/input.json.
  4. Regenerate docs/platform-matrix.md with node tests/platform-matrix/run.mjs; pnpm docs:check fails while it is stale.