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

@axtary/adapters

v0.1.0

Published

Deterministic local adapters for Axtary proxy demos and tests.

Readme

@axtary/adapters

Tool adapters for Axtary proxy demos, tests, and early real-provider wiring.

Early 0.x release: the runtime path is real and tested, but the API is not stable yet and may change between minor versions. Fake adapters remain the safe default, and real GitHub, Slack, Linear, AWS, GCP, and local docs handlers are available behind explicit config.

npm install @axtary/adapters

What It Does

  • Provides fake GitHub PR and content-read handlers.
  • Provides a fake Slack message handler.
  • Provides fake Linear and Jira issue/comment/update handlers.
  • Wraps handlers with ActionPass verification so adapter-side effects require a valid payload-bound pass.
  • Provides real GitHub REST handlers for content reads, branch creation, content writes, and PR creation.
  • Provides a real Slack Web API handler for chat.postMessage.
  • Provides real Linear GraphQL handlers for issue reads, comments, and updates.
  • Provides read-only AWS REST handlers for STS identity and S3 object listing.
  • Provides read-only GCP REST handlers for project reads and Cloud Storage object listing.
  • Provides local docs search/read handlers with configured roots, result/byte caps, path traversal protection, and redaction.
  • Provides non-destructive smoke helpers for GitHub /user, Slack auth.test, Linear viewer, AWS STS GetCallerIdentity, GCP project access, and local docs roots.
  • Classifies provider rate limits, server errors, auth errors, and provider errors for retries and diagnostics.
  • Captures adapter state in memory for tests and local demos.
  • Returns predictable JSON payloads from proxy handlers.

Smoke Helpers

The smoke helpers exercise the same provider clients as the real handlers, but only call read/auth endpoints:

  • smokeGitHubRestCredentials
  • smokeSlackWebCredentials
  • smokeLinearGraphqlCredentials
  • smokeAwsRestCredentials
  • smokeGcpRestCredentials
  • smokeLocalDocsRoots

They are used by axtary smoke to validate credentials before running a real integration.

Quickstart

This example runs as-is with Node 20+:

import { createFakeHandlers, createLocalDocsHandlers, getConnectorCapabilities } from "@axtary/adapters";

// Fake handlers cover the full demo workflow without credentials.
console.log(Object.keys(createFakeHandlers()));

// Real handlers are created the same way, behind explicit config.
const docs = createLocalDocsHandlers({
  roots: [{ name: "docs", path: "./docs" }],
});
console.log(Object.keys(docs));

// The capability registry says which capabilities are real vs demo-only.
console.log(getConnectorCapabilities().filter((c) => c.status === "supported").length, "supported capabilities");

Design Notes

The fake adapters let us prove the authorization flow without credentials. Real adapters should still be wrapped with ActionPass verification so the proxy and adapter boundary both enforce the same action hash, audience, issuer, and expiration.